gsd-execution
Execute work in GSD order — triage, map, plan, decide, implement, validate, close
Файлы1
Открыть в GitHubSKILL.md.opencode/skills/gsd-execution/SKILL.md
GitHubGSD Execution
Workflow Sequence
- Triage:
/project:gsd-triage— create NID, classify, break down - Map:
/project:mapcodebase— understand repo context - Spec:
/project:bmad-spec— define scope and acceptance criteria - Decide:
/project:arch-adr— record architectural decisions - Implement:
/project:impl— make the changes - Validate:
/project:test-full— run tests and verify - Close:
/project:session-close— persist state, write handoff
Rules
- Every phase must leave state behind in
vault/ - No phase should depend on chat history alone
- Each commit should be atomic and independently deployable
- Always check
.planning/REQUIREMENTS.mdfor alignment - Update
.planning/STATE.mdwhen project-level progress is made
State Files
| File | Updated By |
|---|---|
vault/10-Queue/<NID>.md |
gsd-triage, impl |
vault/20-Specs/<NID>-spec.md |
bmad-spec |
vault/30-Architecture/ADR-*.md |
arch-adr |
vault/90-Index/Active NIDs.md |
gsd-triage, session-close |
.planning/STATE.md |
session-close (if project progress) |
Alternative Workflows
Quick fix (no spec/ADR needed):
/project:gsd-triage/project:impl/project:test-full/project:session-close
Audit only (no implementation):
/project:start/project:gsd-triage/project:docker-doctoror/project:workflow-auditor/project:secrets-scan/project:session-close