메뉴
Manage the project's knowledge base. Run post-audit to clean up transient Goldfish checklists (plan.md), merge feature updates back into master design docs, and promote architectural decisions to global project knowledge.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Execute the technical plan for a feature using bounded, task-by-task execution. Acts as the "Goldfish", relying on strict constraints from the "Elephant" (spec.md).
Define requirements, specifications, architecture, and step-by-step task plans for a new feature or modification. Orchestrates the creation of the Elephant (spec.md) and Goldfish Checklist (plan.md).
Establish a project governance document (constitution.md) with immutable architectural articles that all Bolts inherit. Run once per project before bolt-roadmap.
Investigate and document technology choices before architecture is locked. Invoked from bolt-intent Phase 2 when new technology decisions are required. Produces research.md. Optional — skip with documented reason when Bolt extends an established pattern.
Structured post-Bolt retrospective that captures process improvements, proposes constitution amendments, and updates bolt-* skills. Targets the development process — not the project. Distinct from bolt-synthesis.
Create a comprehensive strategic roadmap and diagram for the project by decomposing high-level goals into atomic, sequential/parallel bolts.
| name | bolt-synthesis |
| description | Manage the project's knowledge base. Run post-audit to clean up transient Goldfish checklists (plan.md), merge feature updates back into master design docs, and promote architectural decisions to global project knowledge. |
This workflow executes immediately after a Bolt passes bolt-audit and is marked status: audited. Its primary job is to clean up transient execution files (The Goldfish's memory) and durably record the final state of the architecture (The Elephant).
docs/design/<feature-name>/ or docs/design/<feature-update>/).spec.md or audit-report.md has status: audited. If not, abort and tell the user to run bolt-audit first.The execution checklist (plan.md) is transient. It is no longer needed once the code is audited.
plan.md: Remove plan.md from the feature directory.audit-report.md in the directory (or append its core findings to the spec.md if the user prefers keeping a single file per feature). Ensure its status is explicitly closed out.If the audited directory is a transient feature-update folder (e.g., docs/design/<feature-update>/):
docs/design/<feature>.md).spec.md into the master <feature>.md. Do not just append; rewrite sections for flow and coherence.docs/design/<feature-update>/ directory.If the feature introduces a new architectural pattern, global constraint, or tool choice (logged in the ## Architecture & Decisions (ADR) section):
REQUIREMENTS.md, ARCHITECTURE.md, or .sdlc/CONVENTIONS.md).Next Steps: If process improvements or constitution failures were identified during the lifecycle, queue a bolt-retrospective. Otherwise, the team is ready for the next Bolt (bolt-intent).