메뉴
Streamlined delivery flow for fix PRs created during adversarial refinement, formal hardening, and convergence. Same rigor as story PRs (worktree, AI review, security review) but skips stubs, Red Gate, and wave integration gates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Browser-based visual companion for showing mockups, diagrams, and interactive options during brainstorming, brief creation, and architecture design. Runs a local Node.js server that watches for HTML files and serves them with live reload. Optional — requires Node.js.
Write a verified HANDOFF.md (9 base required fields) and an atomically co-committed wave-state.yaml (6 required fields) to the factory-artifacts branch at wave close. Provides the lossless wave-boundary checkpoint required by BC-5.41.001 and BC-5.41.002.
Computes wave-based implementation order from story dependencies. Groups stories into waves for parallel execution within each wave.
Diagnostic check of STATE.md — validates structure, size, phase numbering, frontmatter, and content routing compliance. Reports HEALTHY, WARNINGS, or NEEDS-COMPACT.
Extract historical content from STATE.md into cycle files (burst logs, adversary passes, session checkpoints, lessons). Slims STATE.md to <200 lines.
Rehydrate session context at the start of a new session after a wave-boundary reset. Reads wave-state.yaml EXCLUSIVELY from the factory-artifacts branch via git show, injects exactly the listed spec files (Set(stories[*].spec_files) ∪ Set(arch_files) ∪ {state_pointer}), and pauses for operator confirmation before any pipeline work begins. Satisfies BC-6.24.001 postconditions 1–8 and VP-088 §1–§4.
| name | fix-pr-delivery |
| description | Streamlined delivery flow for fix PRs created during adversarial refinement, formal hardening, and convergence. Same rigor as story PRs (worktree, AI review, security review) but skips stubs, Red Gate, and wave integration gates. |
When adversarial refinement, formal hardening, or convergence produce findings
that require code fixes on the merged develop branch. Fix tasks are named
FIX-P[phase]-NNN (e.g., FIX-P4-001, FIX-P5-003).
| Aspect | Story PR | Fix PR |
|---|---|---|
| Branch prefix | feature/STORY-NNN | fix/FIX-P4-NNN |
| PR title | feat(STORY-NNN): ... | fix(FIX-P4-NNN): ... |
| Demo required | Always (per AC) | Only if behavior-changing |
| PR description | Full template with diagrams | Streamlined -- links to finding |
| Wave gate after | Yes (wave integration gate) | No -- fix PRs merge individually |
| Stubs + Red Gate | Yes (two-step) | No -- fix goes directly to implementation |
When a phase finding requires a code fix, the orchestrator creates a fix task:
Finding: [finding ID from adversarial/hardening/convergence]
Fix Task: FIX-P[phase]-NNN
Description: [one-line description of what needs fixing]
Source: [adversarial | hardening | convergence]
Severity: [CRITICAL | HIGH | MEDIUM | LOW]
git worktree add .worktrees/FIX-P4-001 -b fix/FIX-P4-001 develop
The implementer works in .worktrees/FIX-P[phase]-NNN/:
fix(FIX-P[phase]-NNN): [description]Demo-recorder records a demo ONLY if the fix is behavior-changing:
cd .worktrees/FIX-P[phase]-NNN/
git push --force-with-lease origin fix/FIX-P[phase]-NNN
Create a streamlined PR description:
## Fix: FIX-P[phase]-NNN
**Finding:** [link to finding report and finding ID]
**Phase:** [4 | 5 | 6]
**Severity:** [CRITICAL | HIGH | MEDIUM | LOW]
### What Changed
[Brief description of the fix]
### Why
[Link to the finding that triggered this fix]
### Testing
- [ ] All existing tests pass
- [ ] New test added for the specific finding (if applicable)
- [ ] Demo recorded (if behavior-changing)
pr-manager spawns github-ops to create the PR, and spawns pr-reviewer to review:
The pr-reviewer (4th model family) reviews the fix PR diff:
If the fix is security-related (CWE/OWASP finding, dependency vulnerability, auth/authz change):
security-reviewer (T2, NO IMPL REASONING):
Input: Fix PR diff only
Action: Verify the fix addresses the security finding without
introducing new vulnerabilities
Output: APPROVE / REQUEST_CHANGES via github-ops
Max 10 review cycles:
pr-manager spawns github-ops to merge, then verifies remote branch deletion, then orchestrator spawns devops-engineer and state-manager for cleanup:
github-ops: "cd <project-path> && gh pr merge --squash --delete-branch"
# Post-merge: verify branch is actually deleted — --delete-branch is async
# (not guaranteed under merge queues; see cli/cli#9073).
# Full hardened sequence (pr-manager.md Step 8 is authoritative):
# 1. Confirm PR state is MERGED (not queued): gh pr view --json state,mergeStateStatus
# 2. Check isCrossRepository: gh pr view --json isCrossRepository,headRepositoryOwner,headRefName
# If fork PR → skip origin deletion (branch lives on contributor's fork).
# 3. Exact-ref check: git ls-remote --exit-code origin refs/heads/<branch>
# (exit code 2 = not found = deleted; avoids prefix-match false positives)
# 4. If still present: wait 5–10 seconds between re-checks, bounded retry (up to 3),
# then force-delete: git push origin --delete <branch> and re-verify
# (idempotent — already-gone/404 is success).
# 5. If branch-protection blocks deletion: log warning and proceed (not fatal).
devops-engineer: "cd <project-path> && git worktree remove .worktrees/FIX-P[phase]-NNN"
state-manager: "Update STATE.md with FIX-P[phase]-NNN completion — merge status, PR number, timestamp"
After fix PRs merge to develop, re-verification depends on the source phase:
Re-run adversary with fresh context -- full adversarial pass on develop.
Route to the specific failing dimension:
Then re-run convergence assessment.
fix/FIX-P[phase]-NNN branch namingfix(FIX-P[phase]-NNN): ... format