一键导入
knowledge-compounding
Use when a non-trivial problem is solved or substantial work should make future sessions easier.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when a non-trivial problem is solved or substantial work should make future sessions easier.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when following the Super Compound BRD -> PRD -> FSD -> GOAL -> IMPLEMENTATION -> VERIFICATION delivery path, artifact traceability, FSD authority, optional ADR handling, zero context bloat issue slicing, or OPEN-* stop conditions.
Use when an approved FSD goal or lightweight issue pointer is ready for implementation.
Use when multi-component work needs cross-component verification of API contracts, data flow, events, auth, config, UI, background jobs, or tests.
Use when /sc-plan needs FSD GOAL-* packets turned into lightweight issue pointers, local Markdown Kanban boards, blocker DAGs, or multi-agent task contracts.
Use when a plan or issue board has 2+ independent execution streams whose time saving exceeds coordination overhead. Dispatches agents in isolated git worktrees only after required delivery gates pass.
Use when an FSD and goal issue board need requirement coverage, goal quality, dependency DAG, sizing, and verification validated before execution.
| name | knowledge-compounding |
| description | Use when a non-trivial problem is solved or substantial work should make future sessions easier. |
Turn proven solutions and reusable session learnings into searchable project memory. Announce use before writing documentation.
Use after a difficult debugging fix, non-obvious root cause, recurring workaround, significant feature, or newly discovered codebase convention. Confirmation such as “that worked” is a signal, not sufficient evidence: skip typos, obvious corrections, and trivial configuration changes.
docs/solutions/; cross-link related records and create a new record only for a distinct root cause.docs/solutions/<category>/; when three or 3+ related issues establish a reusable pattern, add a pattern record.docs/progress.md append-only for session entries while consolidating reusable patterns at its top.Triggered after systematic-debugging, tricky executing-plans work, compound workflows, or before pause handoff. Outputs feed writing-plans, brainstorming, and resume context restoration. Present the created or updated path, then return to the active workflow.