メニュー
Release preparation for Stages I-L of the VibeFlow docs-first workflow
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Register work items, create feature branches, track and advance stages, close work items in the VibeFlow docs-first development workflow
Codebase discovery and analysis for Stage B of the VibeFlow docs-first workflow
Create Feature Specs for Stage E of the VibeFlow docs-first workflow
Create PRDs with success metrics for Stage A of the VibeFlow docs-first workflow
Create tech specs with architecture for Stage C of the VibeFlow docs-first workflow
Document ADRs for non-trivial choices at Stage D of the VibeFlow docs-first workflow
| name | prepare-release |
| description | Release preparation for Stages I-L of the VibeFlow docs-first workflow |
| metadata | {"triggers":["prepare release","deployment","OP-NOTE","close loop","spec reconciliation","Stage I","Stage J","Stage K","Stage L","release checklist"]} |
Release preparation for Stages I-L of the VibeFlow docs-first workflow.
This skill guides release preparation through Stages I-L:
Stage I: Spec Reconciliation
│
├── Compare Feature Spec vs actual implementation
├── Update SPEC documents with any deviations
├── Reconcile ADRs with decisions made
└── Ensure docs match deployed reality
│
▼
Stage J: OP-NOTE Creation
│
├── Create docs/op-notes/op-<feature>.md
├── Document: Preflight, Deploy Steps, Monitoring
├── Document: Runbook, Rollback, Post-Deploy Checks
└── Update op-notes/index.md
│
▼
Stage K: Deploy
│
├── Execute preflight checklist
├── Run deployment steps
├── Execute post-deploy verification
└── Monitor for issues
│
▼
Stage L: Close Loop
│
├── Update master indices
├── Mark feature complete
├── Run retrospective (Large track)
└── Archive or link documentation
/prepare-release check
Validates OP-NOTE completeness and spec reconciliation status.
/prepare-release opnote <feature-slug>
Creates docs/op-notes/op-<feature-slug>.md from template with all required sections.
/prepare-release reconcile <feature-id>
Compares Feature Spec vs actual implementation and updates divergent docs.
Purpose: Ensure documentation matches implementation before release.
Tasks:
Purpose: Document everything operators need for deployment.
Required Sections:
Location: docs/op-notes/op-<feature-slug>.md
Purpose: Execute deployment following OP-NOTE.
Pre-Deploy Checklist:
Post-Deploy Checklist:
Purpose: Finalize feature lifecycle.
Tasks:
docs/features/index.md - mark feature completedocs/op-notes/index.md - link OP-NOTEdocs/specs/index.md if new SPECs createdIndices to Update:
scripts/validate_opnote.py — Validate OP-NOTE completenessscripts/reconcile_specs.py — Check spec reconciliation statusSee assets/:
opnote-template.md — OP-NOTE templateAfter completing each stage, update docs/workflow-state.yaml:
Stage I (Reconcile):
stage: IStage J (OP-NOTE):
stage: Jdocs.opnote: docs/op-notes/op-<slug>.mdCheckpoint #5 (after Stage J):
checkpoint: 5 after passing validationStage K (Deploy):
stage: KStage L (Close):
stage: LCheckpoint #6 (after Stage L):
checkpoint: 6 after passing validationAfter completing each stage, ask the user for permission before committing:
Stage I (Reconcile):
git add docs/ docs/workflow-state.yaml
git commit -m "feat(release): reconcile specs with implementation (#ft-<ID>)"
Stage J (OP-NOTE):
git add docs/op-notes/op-<slug>.md docs/workflow-state.yaml
git commit -m "feat(release): create OP-NOTE for <slug> (#ft-<ID>)"
Stage L (Close):
git add docs/workflow-state.yaml
git commit -m "feat(release): close <slug> (#ft-<ID>)"
git tag v<version>-<slug>
gh pr create --title "[ft-<ID>] <Description>" --body "Closes #ft-<ID>"
Replace <slug>, <ID>, <version>, and <Description> with actual values.
After each sub-stage commit, directly run /manage-work advance <ID>: