Menu
Use after verification to generate contracted documentation, PR, and work-item payloads under the persisted release policy.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when the user asks to 'research codebase', 'scan tech stack', 'import documents', 'discovery questions', or needs guidance on Phase 1 research. Also trigger on 'sdd research', 'brownfield scan', 'import transcript', or 'check ecosystem'.
Use for Phase 2 (Specify): write SPECIFICATION.md with EARS, REQ-IDs, and acceptance criteria. Trigger on sdd_write_spec, sdd_turnkey_spec, sdd_validate_ears, or /specky-specify.
Use for Phase 4 (Design): produce DESIGN.md with architecture, API contracts, data model, and Mermaid diagrams. Trigger on sdd_write_design, sdd_generate_all_diagrams, or /specky-design.
Use for contracted implementation planning, executable TDD bindings, IaC, Docker, devcontainer, local environment, or Codespaces tools after an APPROVE analysis gate.
Use when starting or resuming Specky work, selecting lifecycle/workload/mode/capabilities, diagnosing config/state, or choosing an agent/tool.
This skill should be used when the user asks to 'orchestrate pipeline', 'run full pipeline', 'coordinate phases', 'advance phase', or needs guidance on end-to-end pipeline execution. Also trigger on 'specky orchestrate', 'phase transition', 'LGTM gate', 'pipeline status', or 'which agent for this phase'.
| name | specky-release-engineer |
| description | Use after verification to generate contracted documentation, PR, and work-item payloads under the persisted release policy. |
APPROVE.release capability is enabled with complete configuration.capability_config.release fixes:
Do not substitute develop, stage, main, Gitflow, approval counts, or branch deletion rules unless they are part of the persisted/workspace governance policy.
sdd_create_branch and sdd_create_pr take only explicit feature identity.Use only when work-items is enabled. Platform, subtask policy, and platform-specific fields are persisted. sdd_export_work_items takes feature identity only.
project_key.Never override the target platform per call or route items to an unconfigured tracker.
Generate only documentation supported by complete feature artifacts and the workload. Documentation must contain extracted requirements, design decisions, endpoints, operations, and verification evidence; generic runbooks or fabricated contacts/base URLs are not acceptable.
Run repository-defined build, test, security, and release gates. Report exact commands and results. Do not claim a universal security toolchain, CISO override, staging topology, or coverage percentage unless repository policy defines it.
Include: