원클릭으로
workflow-orchestration
Phase coordination, agent handoffs, and workflow state machine management
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Phase coordination, agent handoffs, and workflow state machine management
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Interactively elicit, capture, and maintain software/system requirements as a living, traceable repository. Use whenever the user wants to gather, write, refine, or organize requirements — including producing or updating an SRS (software/system requirements specification), writing ADRs / architecture decision records, building a requirements traceability graph (DAG), or keeping a decision ledger. Trigger proactively when the working folder already holds requirements artifacts (a `requirements/` folder of YAML, `decisions/` ADRs, an `srs.md`, or `ledger.md`), or when the user shares documents that are clearly specs, RFCs, or feature briefs and wants them structured. Also use for phrases like "let's spec this out", "interview me about what we're building", "capture these requirements", "write a decision record", or "turn these notes into a spec". Not for project management, code review, application code, dependency manifests like requirements.txt, or hardware "system requirements" (RAM/CPU).
Use this skill whenever the user wants to create a bash script that drives an autonomous coding loop — scripts that run Claude Code on a schedule (cron, GitHub Actions, systemd timer) or on-demand to make repository improvements, execute plans, triage issues, or otherwise do agentic work with minimal human intervention. Triggers include phrases like "scout script", "autonomous script", "agent harness", "script that runs on a schedule", "script that implements a plan", ".scripts/*.sh", or any request for a bash script whose body is "run Claude Code with a prompt and commit the results". Always use this skill before writing such a script — it encodes the interview flow, the adversarial-reviewer pattern, and the locking/ledger conventions.
Task structure and atomic commit patterns for granular, verifiable work units
Conflict identification and resolution patterns for requirements, decisions, and plans
Context window management techniques for maintaining efficiency and preventing context bloat
Exploration map management for tracking discussed areas and uncharted territory during DISCUSS phase
SOC 직업 분류 기준
| name | workflow-orchestration |
| description | Phase coordination, agent handoffs, and workflow state machine management |
| triggers | ["workflow","phase transition","orchestration","coordination"] |
This skill provides patterns for coordinating workflow phases, managing agent handoffs, and maintaining the workflow state machine.
┌─────────────────────────────────────────────────┐
│ │
v │
┌──────────┐ ┌─────────┐ ┌──────────┐ ┌────────┐ │ ┌──────────┐
│ INIT │ -> │ DISCUSS │ -> │ PLAN │ -> │EXECUTE │-┘>│ VERIFY │
└──────────┘ └─────────┘ └──────────┘ └────────┘ └──────────┘
^ ^ │ │
│ │ │ │
└───────────────┴──────────────┘ │
(on issues found) │
v
┌──────────┐
│ COMPLETE │
└──────────┘
| From | To | Condition |
|---|---|---|
| INIT | DISCUSS | Initialization complete |
| DISCUSS | PLAN | Requirements captured |
| PLAN | EXECUTE | Plan approved |
| EXECUTE | VERIFY | All tasks complete |
| EXECUTE | DISCUSS | Major scope change needed |
| EXECUTE | PLAN | Task restructure needed |
| VERIFY | COMPLETE | Sign-off received |
| VERIFY | EXECUTE | Issues need fixing |
Before entering any phase:
1. VERIFY previous phase complete
- Check completion criteria
- Verify artifacts exist
- No active blockers
2. CREATE checkpoint in ITEM-XXX.md
- Snapshot current state
- Record transition reason
- Note timestamp
3. UPDATE phase status
- Set new phase
- Reset progress to 0%
- Record start time
4. PREPARE phase context
- Load relevant state files
- Identify agents needed
- Clear stale context
Before exiting any phase:
1. VERIFY completion criteria
- Phase-specific requirements met
- Artifacts created
- No pending decisions
2. CREATE phase summary
- What was accomplished
- Decisions made
- Artifacts produced
3. HANDOFF to next phase
- What next phase needs to know
- Key context to carry forward
- Warnings or considerations
## Agent Spawn: [agent-name]
**Purpose**: [Clear objective]
**Context provided**:
- Phase: [current phase]
- Task: [specific task if applicable]
- Key decisions: [relevant decisions]
- Files: [files to read]
**Expected deliverable**:
- [What agent should produce]
- [Format expected]
**Constraints**:
- [Time/scope limits]
- [Must follow conventions]
- [Report blockers immediately]
## Agent Result: [agent-name]
**Status**: [SUCCESS/PARTIAL/FAILED]
**Deliverables**:
- [What was produced]
- [Where it's stored]
**Key findings**:
- [Important discovery]
- [Important discovery]
**Issues encountered**:
- [Issue if any]
**Next recommended action**:
- [What to do next]
When multiple agents needed:
## Coordination Plan
**Agents involved**:
1. [Agent A]: [Purpose]
2. [Agent B]: [Purpose]
**Sequence**:
A -> B (B depends on A's output)
**Handoff points**:
- A completes: [deliverable] -> B starts
- B completes: [deliverable] -> next phase
**Fallback**:
- If A fails: [contingency]
- If B fails: [contingency]
Watch for:
## Blocker Detected
**Type**: [Technical/Decision/External/Conflict]
**Phase**: [current phase]
**Impact**: [what's blocked]
**Options**:
1. Resolve blocker directly
2. Work around blocker
3. Pause workflow
4. Escalate to user
**Recommended**: [option]
In ITEM-XXX.md:
### BLOCKER-XXX: [Title]
**Status**: ACTIVE -> RESOLVED
**Detected**: [timestamp]
**Resolved**: [timestamp]
**Resolution**: [what was done]
**Impact on workflow**: [any changes made]
| Phase | Progress Based On |
|---|---|
| INIT | Steps completed / total steps |
| DISCUSS | Areas explored / total areas |
| PLAN | Tasks defined / estimated total |
| EXECUTE | Tasks completed / total tasks |
| VERIFY | Checks passed / total checks |
## Workflow Progress
**Overall**: [X]%
**Phase**: [current phase] at [Y]%
**Phase breakdown**:
- [x] INIT: 100%
- [x] DISCUSS: 100%
- [ ] PLAN: 75%
- [ ] EXECUTE: 0%
- [ ] VERIFY: 0%
**Blockers**: [count]
**Next milestone**: [description]
When needing to return to earlier phase:
## Phase Rollback
**From**: [current phase]
**To**: [target phase]
**Reason**: [why rolling back]
**Actions**:
1. Save current state as checkpoint
2. Preserve completed work
3. Update phase status
4. Clear invalid artifacts (if any)
5. Resume from target phase
## Workflow Recovery
**Failure point**: [where it failed]
**Error**: [what happened]
**Recovery options**:
1. Retry from checkpoint
2. Skip failed item
3. Manual intervention
4. Abort with state preserved
**State preserved at**: .flow/FLOW.md and .flow/items/ITEM-XXX.md
**Resume command**: /flow-workflow:go
For /flow-workflow:quick:
## Quick Mode Flow
**Simplified phases**:
ASSESS -> CLARIFY -> IMPLEMENT -> VERIFY
**Shortcuts taken**:
- No FLOW.md or ITEM-XXX.md files created
- No detailed requirements gathering
- Direct execution
- Brief verification
**Escalation trigger**:
If complexity exceeds quick mode, escalate to full workflow with /flow-workflow:start