session-discipline
从项目概念描述生成初始项目规划文档(PVS、ADR、技术规范、路线图)。在开始新项目、docs/planning/包含占位符文件或用户请求项目规划文档生成时使用。
📖 中文导读:从项目概念描述生成初始项目规划文档(PVS、ADR、技术规范、路线图)。在开始新项目、docs/planning/包含占位符文件或用户请求项目规划文档生成时使用。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: session-discipline description: Enforce session-first workflow (plan → implement → verify → document). Use whenever starting non-trivial work, debugging >15 minutes, or doing cross-cutting changes.
Session Discipline
Scope
- Ensure every non-trivial task has a session folder under
docs/sessions/ - Keep evidence (commands/tests) and outcomes discoverable
- Reduce “handover friction” by making every action resumable from docs
Inputs
- Desired session slug (short, descriptive)
- Session type/category and objective one-liner
Procedure
- Create a session directory with the official CLI.
- Fill in
PLAN.md(objective, done-when, change set, risks, tests). - Log commands + findings in
WORKING_NOTES.md. - Summarize outcomes + follow-ups with named owners.
Validation
- Confirm session appears in
docs/sessions/SESSIONS_HUB.md. - Ensure
FOLLOW_UPS.mdhas owners if anything is deferred.
Escalation / Research request
If you need deeper background and existing docs aren’t sufficient:
- Add a follow-up: “Request research agent to expand Skill ”
- Include: expected triggers, target files, and what validation should exist
References
- Session-first requirement:
AGENTS.md - docs-memory lessons:
docs/agi/LESSONS.md