القائمة
Use when starting, planning, executing, verifying, archiving, or shipping development work that should coordinate GSD Core, OpenSpec, and Superpowers
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | gsd-spec-workflow |
| description | Use when starting, planning, executing, verifying, archiving, or shipping development work that should coordinate GSD Core, OpenSpec, and Superpowers |
OpenSpec owns product intent. GSD Core owns project execution state. Superpowers owns engineering discipline.
Do not implement from chat memory. Use the current OpenSpec change, GSD phase plan, existing code, tests, and explicit user clarification as source material.
| Situation | Required action |
|---|---|
| New feature or behavior change | Create or update an OpenSpec change first |
| Ambiguous request | Use GSD discussion before planning implementation |
| Multi-step work | Create a GSD phase plan that references the OpenSpec change |
| Coding task | Use Superpowers TDD before writing production code |
| Unexpected failure | Use Superpowers systematic debugging |
| Completion claim | Use Superpowers verification before completion |
| Archive or ship | Run spec archive gate after GSD verification |
Before implementation, identify:
If any item is missing, stop and create or request it before implementation.
When OpenSpec and the GSD phase plan disagree, stop. Prefer the newer reviewed source only when provenance is clear. Otherwise ask for a decision.
Read references/phase-map.md when mapping OpenSpec work to GSD phases.
Read references/handoff-contract.md before handing work between agents.
Use when converting an OpenSpec change, proposal, design, specs, or tasks into implementation work before coding starts
Use when an OpenSpec change or GSD phase is claimed complete, ready to archive, ready to ship, ready to commit, or ready for pull request
Use when reviewing implemented code, completed tasks, test coverage, or diffs for an OpenSpec change before continuing, archiving, or shipping
