메뉴
Canonical reference for all contribution artifact schemas, templates, folder naming conventions, file format rules, and workflow patterns (progressive disclosure, two-gate system, constraint discovery, routing) used across dev-strategy workflow skills.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Enables structured contributions to dev-strategy implementation plans with proper documentation and knowledge transfer. Use when you need to "contribute to dev-strategy", "implement this phase", "review the code", "audit the implementation", "add to the dev plan", or make specialized contributions (testing, auditing, documenting) to existing dev-strategy roadmaps. Generates decision logs and context handoffs with mandatory documentation.
Creates sufficient implementation plans for complex coding projects by analyzing your codebase, gathering constraints, and proposing execution strategies. Use when you need to "plan how to build", "create implementation roadmap", "break down this feature", "how should I approach building", or structure multi-phase development, refactoring, or architectural changes. Produces code context, behavioral specs, decision logs, and implementation roadmaps.
Enables collaborative design contributions to dev-strategy implementation plans through human-in-the-loop sessions. Use when roadmap phases have "Design" objectives, you need to "design the [component]", "figure out the [approach]", "determine the [architecture]", or refinement before implementation. Works with `.plans/plan-[FEATURE-NAME]/` directories only. Produces lean design docs (< 100 lines) through interactive exploration with ruthless focus on simplicity.
Reference guide for design philosophy applied across all dev-strategy workflow skills. Use when you need to understand YAGNI, Last Responsible Moment, Kent Beck's 4 Simple Design Rules, Sufficient Design, and Just-In-Time Architecture principles. Provides context for planning, design, and implementation decisions.
Mandatory skill to use whenever you interact with any TUI built on the tui-harness/tui-elm/tui-design framework (diffviz-review-tui, patina-detect-tui, and future ELM-style TUIs in this workspace), whether to add code to it, test it, or plan a change
Harvests architectural decisions and writes lean Architecture Decision Records to docs/adr/. Works in two modes — from a dev-strategy plan (reads decision-log.yaml files) or from a raw codebase (mines git history, comments, and docs). Use when a plan is done or when you want to capture past decisions from any codebase.
| name | contribution-system |
| description | Canonical reference for all contribution artifact schemas, templates, folder naming conventions, file format rules, and workflow patterns (progressive disclosure, two-gate system, constraint discovery, routing) used across dev-strategy workflow skills. |
| skills-depend-on | ["design-principles"] |
Standardized conventions for contribution artifacts, folder naming, directory structure, and workflow patterns used across all dev-strategy workflow skills.
This skill is the canonical reference for:
Load this skill when:
Structure & Naming:
decision-log.yaml schema and why it's unifiedArtifact Schemas by Type:
For decision-log.yaml (implementation contributions):
diffviz templates decision-log > decision-log.yamldiffviz validate decision-log decision-log.yamlReference templates (design, strategy, other artifacts):
Design templates:
Strategy (planning) templates:
When you need information about a feature, use this table to find the right artifact:
| Question | Answer From | Location |
|---|---|---|
| "What am I building?" | context-document.md | Plan root |
| "What's the overall execution strategy?" | implementation-roadmap.md | Plan root |
| "What functions/classes are relevant?" | code-context.md | Plan root |
| "Why was this architecture chosen?" | decision-log.yaml | Plan root |
| "What changed in this contribution?" | decision-log.yaml | contributions/NNN-.../ |
| "Where must a reviewer scrutinize decision #3?" | decision-log.yaml → code_impacts | contributions/NNN-.../ |
| "What should the next phase focus on?" | context-handoff.md | contributions/NNN-.../ |
| "What's the design for error handling?" | design-doc.md | contributions/NNN-design-.../ |
| "What design constraints exist?" | decision-log.yaml (design variant) | contributions/NNN-design-.../ |
| "How do I get oriented quickly?" | context-handoff.md | contributions/NNN-.../ |
Progressive Disclosure Rule: Always start with context-handoff.md in a contribution, then dive into decision-log.yaml for details.
This skill also defines workflow patterns used across all dev-strategy skills. Load these references as needed: