MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Strategic requirement roadmap with iterative decomposition and issue creation.
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/roadmap-with-file .claude/skills/roadmap-with-file && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .claude/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-fileType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/roadmap-with-file .agents/skills/roadmap-with-file && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .agents/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/roadmap-with-file .cursor/skills/roadmap-with-file && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .cursor/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/catlog22/Claude-Code-Workflow.git --path .codex/skills/roadmap-with-file--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/roadmap-with-file .gemini/skills/roadmap-with-file && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .gemini/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-fileInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/roadmap-with-file .github/skills/roadmap-with-file && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .github/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/roadmap-with-file .opencode/skills/roadmap-with-file && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "roadmap-with-file" agent skill from https://github.com/catlog22/Claude-Code-Workflow/tree/main/.codex/skills/roadmap-with-file into .opencode/skills/roadmap-with-file/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "roadmap-with-file", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
roadmap-with-fileStrategic requirement roadmap with iterative decomposition and issue creation.
Roadmap With File is an agent skill from catlog22/Claude-Code-Workflow. Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable).
Its SKILL.md is about 7.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript, markdown, bash and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Roadmap With File loads about 7.5k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 932 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 932 words, ~7,501 tokens.
.claude/skills/roadmap-with-file/SKILL.md (or your agent's skills folder).When --yes or -y: Auto-confirm strategy selection, use recommended mode, skip interactive refinement rounds. This skill is planning-only — it NEVER executes code or modifies source files. Output is the roadmap + issues for user review.
$roadmap-with-file "Implement user authentication system with OAuth and 2FA"
$roadmap-with-file -m progressive "Build real-time notification system"
$roadmap-with-file -m direct "Refactor payment module"
$roadmap-with-file -m auto "Add data export feature"
$roadmap-with-file --continue "auth system"
$roadmap-with-file -y "Implement caching layer"Flags:
-y, --yes: Skip all confirmations (auto mode)-c, --continue: Continue existing session-m, --mode: Strategy selection (progressive / direct / auto)Context Source: cli-explore-agent (optional) + requirement analysis
Output Directory: .workflow/.roadmap/{session-id}/
Core Output: roadmap.md (single source, human-readable) + issues.jsonl (global, machine-executable)
Create a new subagent with task assignment.
const agentId = spawn_agent({
agent_type: "{agent_type}",
message: `
## TASK ASSIGNMENT
### MANDATORY FIRST STEPS (Agent Execute)
1. Read: .workflow/project-tech.json
2. Read: .workflow/project-guidelines.json
## TASK CONTEXT
${taskContext}
## DELIVERABLES
${deliverables}
`
})Get results from subagent (only way to retrieve results).
const result = wait_agent({
timeout_ms: 1800000 // 30 minutes
})
if (result.timed_out) {
// Handle timeout via 4-step cascade: status probe → force finalize → close
}Assign new work to active subagent (for clarification or follow-up).
followup_task({
target: agentId,
message: `
## CLARIFICATION ANSWERS
${answers}
## NEXT STEP
Continue with plan generation.
`
})Clean up subagent resources (irreversible).
close_agent({ target: agentId })| Artifact | Purpose | Consumer |
|---|---|---|
roadmap.md | ⭐ Human-readable strategic roadmap with all context | Human review, csv-wave-pipeline handoff |
.workflow/issues/issues.jsonl | Global issue store (appended) | csv-wave-pipeline, issue commands |
| Original File | Why Removed | Where Content Goes |
|---|---|---|
strategy-assessment.json | Duplicates roadmap.md content | Embedded in roadmap.md Strategy Assessment section |
exploration-codebase.json | Single-use intermediate | Embedded in roadmap.md Codebase Context appendix |
Strategic requirement roadmap with iterative decomposition. Creates a single roadmap.md that evolves through discussion, with issues persisted to global issues.jsonl for execution.
Core workflow: Understand → Decompose → Iterate → Validate → Handoff
Key features:
web.runissues.jsonl for execution pipelinefunctions.update_plan for real-time phase progress visibility┌─────────────────────────────────────────────────────────────────────────┐
│ ROADMAP ITERATIVE WORKFLOW │
├─────────────────────────────────────────────────────────────────────────┤
│ │
│ Session Init │
│ ├─ Parse flags, generate session ID │
│ ├─ functions.exec_command (mkdir session folder) │
│ └─ functions.update_plan (5 phases: Understand → Decompose → │
│ Refine → Handoff → GATE) │
│ │
│ Phase 1: Requirement Understanding & Strategy │
│ ├─ Parse requirement: goal / constraints / stakeholders │
│ ├─ Assess uncertainty level → recommend mode │
│ ├─ User confirms strategy via functions.request_user_input │
│ └─ Initialize roadmap.md with Strategy Assessment │
│ │
│ Phase 2: Decomposition & Issue Creation │
│ ├─ Optional codebase exploration (functions.exec_command detection) │
│ ├─ cli-roadmap-plan-agent executes decomposition │
│ ├─ Progressive: 2-4 layers (MVP→Optimized) with convergence │
│ ├─ Direct: Topological task sequence with convergence │
│ ├─ Create issues via ccw issue create → issues.jsonl │
│ └─ Update roadmap.md with Roadmap table + Issue references │
│ │
│ Phase 3: Iterative Refinement (Multi-Round, Decision Recording) │
│ ├─ Present roadmap to user (Cumulative Context) │
│ ├─ Feedback via functions.request_user_input: │
│ │ Approve | Adjust Scope | Refine Criteria | Research/Re-decompose │
│ ├─ External research via web.run (optional — patterns, practices) │
│ ├─ Record decisions in Iteration History (Record-Before-Continue) │
│ └─ Repeat until approved (max 5 rounds) │
│ │
│ Phase 4: Handoff (PLANNING ENDS HERE) │
│ ├─ Final roadmap.md with Issue ID references │
│ └─ MANDATORY Terminal Gate: 执行计划 / 查看Issue / 完成 │
│ ├─ Execute Plan → display csv-wave-pipeline command │
│ ├─ View Issues → ccw issue list │
│ └─ Done → end workflow │
│ │
└─────────────────────────────────────────────────────────────────────────┘| Mode | Strategy | Best For | Decomposition |
|---|---|---|---|
| Progressive | MVP → Usable → Refined → Optimized | High uncertainty, need validation | 2-4 layers, each with full convergence |
| Direct | Topological task sequence | Clear requirements, confirmed tech | Tasks with explicit inputs/outputs |
Auto-selection logic:
.workflow/.roadmap/RMAP-{date}-{slug}/
└── roadmap.md # ⭐ Single source of truth
# - Strategy Assessment (embedded)
# - Roadmap Table
# - Convergence Criteria per Issue
# - Codebase Context (appendix, if applicable)
# - Iteration History
.workflow/issues/issues.jsonl # Global issue store (appended)
# - One JSON object per line
# - Consumed by csv-wave-pipeline, issue commands# Requirement Roadmap
**Session**: RMAP-{date}-{slug}
**Requirement**: {requirement}
**Strategy**: {progressive|direct}
**Status**: {Planning|Refining|Ready}
**Created**: {timestamp}
---
## Strategy Assessment
- **Uncertainty Level**: {high|medium|low}
- **Decomposition Mode**: {progressive|direct}
- **Assessment Basis**: {factors summary}
- **Goal**: {extracted goal}
- **Constraints**: {extracted constraints}
- **Stakeholders**: {extracted stakeholders}
---
## Roadmap
### Progressive Mode
| Wave | Issue ID | Layer | Goal | Priority | Dependencies |
|------|----------|-------|------|----------|--------------|
| 1 | ISS-xxx | MVP | ... | 2 | - |
| 2 | ISS-yyy | Usable | ... | 3 | ISS-xxx |
### Direct Mode
| Wave | Issue ID | Title | Type | Dependencies |
|------|----------|-------|------|--------------|
| 1 | ISS-xxx | ... | infrastructure | - |
| 2 | ISS-yyy | ... | feature | ISS-xxx |
---
## Convergence Criteria
### ISS-xxx: {Issue Title}
- **Criteria**: [testable conditions]
- **Verification**: [executable steps/commands]
- **Definition of Done**: [business language, non-technical]
### ISS-yyy: {Issue Title}
...
---
## Risks
| Risk | Severity | Mitigation |
|------|----------|------------|
| ... | ... | ... |
---
## Iteration History
### Round 1 - {timestamp}
**User Feedback**: {feedback summary}
**Changes Made**: {adjustments}
**Status**: {approved|continue iteration}
---
## Codebase Context (Optional)
*Included when codebase exploration was performed*
- **Relevant Modules**: [...]
- **Existing Patterns**: [...]
- **Integration Points**: [...]Path: .workflow/issues/issues.jsonl
Format: JSONL (one complete JSON object per line)
Encoding: UTF-8
Mode: Append-only (new issues appended to end){
"id": "ISS-YYYYMMDD-NNN",
"title": "[LayerName] goal or [TaskType] title",
"status": "pending",
"priority": 2,
"context": "Markdown with goal, scope, convergence, verification, DoD",
"source": "text",
"tags": ["roadmap", "progressive|direct", "wave-N", "layer-name"],
"extended_context": {
"notes": {
"session": "RMAP-{date}-{slug}",
"strategy": "progressive|direct",
"wave": 1,
"depends_on_issues": []
}
},
"lifecycle_requirements": {
"test_strategy": "unit",
"regression_scope": "affected",
"acceptance_type": "automated",
"commit_strategy": "per-issue"
}
}# By ID (detail view)
ccw issue list ISS-20260227-001
# List all with status filter
ccw issue list --status planned,queued
ccw issue list --brief # JSON minimal output
# Queue operations (wave-based execution)
ccw issue queue list # List all queues
ccw issue queue dag # Get dependency graph (JSON)
ccw issue next --queue <queue-id> # Get next task
# Execute
ccw issue queue add <issue-id> # Add to active queue
ccw issue done <item-id> # Mark completedNote: Issues are tagged with
wave-Nintags[]field for filtering. Use--brieffor programmatic parsing.
const getUtc8ISOString = () => new Date(Date.now() + 8 * 60 * 60 * 1000).toISOString()
// Parse flags
const AUTO_YES = $ARGUMENTS.includes('--yes') || $ARGUMENTS.includes('-y')
const continueMode = $ARGUMENTS.includes('--continue') || $ARGUMENTS.includes('-c')
const modeMatch = $ARGUMENTS.match(/(?:--mode|-m)\s+(progressive|direct|auto)/)
const requestedMode = modeMatch ? modeMatch[1] : 'auto'
// Clean requirement text (remove flags)
const requirement = $ARGUMENTS
.replace(/--yes|-y|--continue|-c|--mode\s+\w+|-m\s+\w+/g, '')
.trim()
const slug = requirement.toLowerCase()
.replace(/[^a-z0-9\u4e00-\u9fa5]+/g, '-')
.substring(0, 40)
const dateStr = getUtc8ISOString().substring(0, 10)
const sessionId = `RMAP-${dateStr}-${slug}`
const sessionFolder = `.workflow/.roadmap/${sessionId}`
// Auto-detect continue mode
if (continueMode || file_exists(`${sessionFolder}/roadmap.md`)) {
// Resume existing session
const existingRoadmap = Read(`${sessionFolder}/roadmap.md`)
// Extract current phase and continue from there
}
functions.exec_command(`mkdir -p ${sessionFolder}`)
// Initialize progress tracking (MANDATORY)
functions.update_plan([
{ id: "phase-1", title: "Phase 1: Requirement Understanding & Strategy", status: "in_progress" },
{ id: "phase-2", title: "Phase 2: Decomposition & Issue Creation", status: "pending" },
{ id: "phase-3", title: "Phase 3: Iterative Refinement", status: "pending" },
{ id: "phase-4", title: "Phase 4: Handoff", status: "pending" },
{ id: "next-step", title: "GATE: Post-Completion Next Step", status: "pending" }
])Objective: Parse requirement, assess uncertainty, select decomposition strategy, initialize roadmap.md.
Steps:
Parse Requirement
Assess Uncertainty
const uncertaintyFactors = {
scope_clarity: 'low|medium|high',
technical_risk: 'low|medium|high',
dependency_unknown: 'low|medium|high',
domain_familiarity: 'low|medium|high',
requirement_stability: 'low|medium|high'
}
// Calculate recommendation
const highCount = Object.values(uncertaintyFactors).filter(v => v === 'high').length
const lowCount = Object.values(uncertaintyFactors).filter(v => v === 'low').length
let recommendedMode
if (highCount >= 3) recommendedMode = 'progressive'
else if (lowCount >= 3) recommendedMode = 'direct'
else recommendedMode = 'progressive' // default safer choiceStrategy Selection (skip if -m specified or AUTO_YES)
let selectedMode
if (requestedMode !== 'auto') {
selectedMode = requestedMode
} else if (AUTO_YES) {
selectedMode = recommendedMode
} else {
const answer = functions.request_user_input({
questions: [{
header: "Strategy", // max 12 chars
question: `Decomposition strategy: Uncertainty=${uncertaintyLevel}, Recommended=${recommendedMode}`,
multiSelect: false,
options: [
{ label: recommendedMode === 'progressive' ? "Progressive (Recommended)" : "Progressive", description: "MVP → Usable → Refined → Optimized layers" },
{ label: recommendedMode === 'direct' ? "Direct (Recommended)" : "Direct", description: "Topological task sequence" }
]
}]
})
selectedMode = answer // parsed from user selection
}Initialize roadmap.md
const roadmapContent = `# Requirement RoadmapSession: ${sessionId} Requirement: ${requirement} Strategy: ${selectedMode} Status: Planning Created: ${getUtc8ISOString()}
To be populated after Phase 2 decomposition
To be populated after Phase 2 decomposition
To be populated after Phase 2 decomposition
To be populated during Phase 3 refinement
To be populated if codebase exploration was performed `
Write(${sessionFolder}/roadmap.md, roadmapContent)
**Success Criteria**:
- roadmap.md created with Strategy Assessment
- Strategy selected (progressive or direct)
- Uncertainty factors documented
---
### Phase 2: Decomposition & Issue Creation
**Objective**: Execute decomposition via `cli-roadmap-plan-agent`, create issues, update roadmap.md.
**Steps**:
1. **Optional Codebase Exploration** (if codebase detected)
```javascript
// Update progress
functions.update_plan([{ id: "phase-2", title: "Phase 2: Decomposition & Issue Creation", status: "in_progress" }])
const hasCodebase = functions.exec_command(`
test -f package.json && echo "nodejs" ||
test -f go.mod && echo "golang" ||
test -f Cargo.toml && echo "rust" ||
test -f pyproject.toml && echo "python" ||
test -d src && echo "generic" ||
echo "none"
`).trim()
let codebaseContext = null
if (hasCodebase !== 'none') {
const exploreAgentId = spawn_agent({
agent_type: "cli_explore_agent",
message: `
## TASK ASSIGNMENT
### MANDATORY FIRST STEPS (Agent Execute)
1. Read: .workflow/project-tech.json
2. Read: .workflow/project-guidelines.json
---
## Exploration Context
- **Requirement**: ${requirement}
- **Strategy**: ${selectedMode}
- **Project Type**: ${hasCodebase}
- **Session**: ${sessionFolder}
## Exploration Focus
- Identify modules/components related to the requirement
- Find existing patterns that should be followed
- Locate integration points for new functionality
- Assess current architecture constraints
## Output
Return findings as JSON with schema:
{
"project_type": "${hasCodebase}",
"relevant_modules": [{name, path, relevance}],
"existing_patterns": [{pattern, files, description}],
"integration_points": [{location, description, risk}],
"architecture_constraints": [string],
"tech_stack": {languages, frameworks, tools}
}
`
})
const exploreResult = wait_agent({
timeout_ms: 1800000 // 30 minutes
})
close_agent({ target: exploreAgentId })
if (exploreResult.status[exploreAgentId].completed) {
codebaseContext = exploreResult.status[exploreAgentId].completed
}
}const decompositionAgentId = spawn_agent({
agent_type: "cli_roadmap_plan_agent",
message: `${JSON.stringify(strategyAssessment, null, 2)}
${codebaseContext ? JSON.stringify(codebaseContext, null, 2) : 'No codebase detected - pure requirement decomposition'}
${selectedMode === 'progressive' ? `Progressive Mode:
`Direct Mode:
Analyze requirement and build decomposition context
Execute decomposition (internal reasoning)
Validate records, check convergence quality
For each decomposed item:
Update roadmap.md with Issue ID references
Return brief completion summary with Issue IDs ` })
const decompositionResult = wait_agent({ timeout_ms: 1800000 // 30 minutes for complex decomposition })
close_agent({ target: decompositionAgentId })
if (!decompositionResult.status[decompositionAgentId].completed) { throw new Error('Decomposition agent failed to complete') }
const issueIds = decompositionResult.status[decompositionAgentId].completed.issueIds || []
Success Criteria:
.workflow/issues/issues.jsonlObjective: Multi-round user feedback to refine roadmap.
Cumulative Context Rule: Each round's presentation MUST include ALL prior feedback and changes. Never present in isolation — always show cumulative state.
Decision Recording: Every user feedback choice and resulting change MUST be recorded in Iteration History with Decision Record format:
> **Decision**: [Description]
> - **Context**: [What triggered this]
> - **Options**: [What was considered]
> - **Chosen**: [Selected] — **Reason**: [Why]
> - **Impact**: [What changed in roadmap]Steps:
Display Current Roadmap
Feedback Loop (skip if AUTO_YES)
// Update progress
functions.update_plan([{ id: "phase-3", title: "Phase 3: Iterative Refinement", status: "in_progress" }])
let round = 0
let approved = false
while (!approved && round < 5) {
round++
// Dynamic options — include research if not yet done
const baseOptions = [
{ label: "Approve", description: "Proceed to handoff" },
{ label: "Adjust Scope", description: "Modify issue scopes" },
{ label: "Refine Criteria", description: "Improve convergence criteria/verification" }
]
// Add research option if architecture decisions need external validation
if (!researchDone) {
baseOptions.push({ label: "Research", description: "Search for architecture patterns and best practices" })
} else {
baseOptions.push({ label: "Re-decompose", description: "Change strategy/layering" })
}
const feedback = functions.request_user_input({
questions: [{
header: "Validate", // max 12 chars
question: `Roadmap round ${round}: ${issueIds.length} issues across ${waveCount} waves. Your decision:`,
multiSelect: false,
options: baseOptions
}]
})
if (feedback === 'Approve') {
approved = true
} else if (feedback === 'Research') {
// Execute web.run for architecture patterns and best practices
const researchQueries = generateResearchQueries(requirement, selectedMode)
researchQueries.forEach(query => {
const results = web.run({ search_query: query })
// Extract: architecture patterns, best practices, risk mitigations
})
researchDone = true
// Record research findings in roadmap.md Iteration History
} else {
// For Adjust Scope, Refine Criteria, Re-decompose:
// Collect details via functions.request_user_input or free text
// CONSTRAINT: All modifications ONLY touch roadmap.md and issues.jsonl
// NEVER modify source code or project files during interactive rounds
// Record decision in Iteration History using Decision Record format
}
// Update Iteration History in roadmap.md (Record-Before-Continue)
const iterationEntry = `User Feedback: ${feedback} Changes Made: ${changesMade} Decision: ${decisionRecord} Status: ${approved ? 'approved' : 'continue iteration'} ` // Append to Iteration History section in roadmap.md }
3. **Finalize Iteration History**
```javascript
// Update final status in roadmap.md
Edit({
path: `${sessionFolder}/roadmap.md`,
old_string: "**Status**: Planning",
new_string: "**Status**: Ready"
})Success Criteria:
Objective: Present final roadmap, execute MANDATORY terminal gate for next step selection.
Steps:
Display Summary
## Roadmap Complete
- **Session**: RMAP-{date}-{slug}
- **Strategy**: {progressive|direct}
- **Issues Created**: {count} across {waves} waves
- **Roadmap**: .workflow/.roadmap/RMAP-{date}-{slug}/roadmap.md
| Wave | Issue Count | Layer/Type |
|------|-------------|------------|
| 1 | 2 | MVP / infrastructure |
| 2 | 3 | Usable / feature |MANDATORY Terminal Gate (CRITICAL — MUST execute, workflow MUST NOT end without this)
// Update progress
functions.update_plan([
{ id: "phase-4", title: "Phase 4: Handoff", status: "completed" },
{ id: "next-step", title: "GATE: Post-Completion Next Step", status: "in_progress" }
])
const nextStep = functions.request_user_input({
questions: [{
header: "Next Step", // max 12 chars
question: `${issueIds.length} issues ready in roadmap. What would you like to do next?`,
multiSelect: false,
options: [
{ label: "Execute Plan", description: "Hand off to execution pipeline (csv-wave-pipeline)" },
{ label: "View Issues", description: "Display issue details before deciding" },
{ label: "Done", description: "Planning complete, all artifacts saved" }
]
}]
})
// Handle next step
if (nextStep === "Execute Plan") {
// Display execution command for user to run manually
// "Run: $csv-wave-pipeline '${requirement}'" or "/issue:execute"
// This skill is planning-only — NEVER auto-launch execution
} else if (nextStep === "View Issues") {
functions.exec_command(`ccw issue list --session ${sessionId}`)
// After viewing, show execution commands
}
// "Done" → end workflow
// Mark terminal gate complete
functions.update_plan([
{ id: "next-step", title: "GATE: Post-Completion Next Step", status: "completed" }
])Success Criteria:
| Error | Resolution |
|---|---|
| cli-explore-agent fails | Skip code exploration, proceed with pure requirement decomposition |
| cli-roadmap-plan-agent fails | Retry once, fallback to manual decomposition prompt |
| No codebase | Normal flow, skip exploration step |
| Web research fails | Continue without external findings, rely on inline analysis |
| Research conflicts with plan | Present as competing evidence, let user decide direction |
| Circular dependency detected | Prompt user, re-decompose |
| User timeout in feedback loop | Save roadmap.md, show --continue command |
| Max rounds reached | Force proceed with current roadmap |
| Session folder conflict | Append timestamp suffix |
roadmap.md and issues.jsonl. NEVER modify source code, configuration files, or any project files during any phase. Code changes happen only after handoff when user manually runs $csv-wave-pipeline or other execution skillsWhen to Use Roadmap vs Other Skills:
| Scenario | Recommended Skill |
|---|---|
| Strategic planning, need issue tracking | $roadmap-with-file |
| Quick task breakdown, immediate execution | $lite-plan |
| Collaborative multi-agent planning | $collaborative-plan-with-file |
| Full specification documents | $spec-generator |
| Code implementation from existing plan | $workflow-lite-plan |
Now plan roadmap for: $ARGUMENTS
© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .codex/skills/roadmap-with-file of catlog22/Claude-Code-Workflow.
Open the folder on GitHubat commit 07491b0
Roadmap With File next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Roadmap With File this skillcatlog22/Claude-Code-Workflow | 2.1k | — | ~7.5k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 35 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 795 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
catlog22/Claude-Code-Workflow
CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.
catlog22/Claude-Code-Workflow
Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Check workflow delegation prompts against agent role definitions for content separation violations.
catlog22/Claude-Code-Workflow
Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.
catlog22/Claude-Code-Workflow
Unified issue discovery and creation. An agent skill from catlog22/Claude-Code-Workflow.
Categories
Strategic requirement roadmap with iterative decomposition and issue creation. Roadmap With File is an agent skill from catlog22/Claude-Code-Workflow. Strategic requirement roadmap with iterative decomposition and issue creation.
Roadmap With File fits situations like: agent Workflows work in your project.
Run `npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a claude-code`. Or copy the skill folder (.codex/skills/roadmap-with-file in catlog22/Claude-Code-Workflow) into .claude/skills/roadmap-with-file in your project. Claude Code loads it when a task matches its description.
Run `npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a codex`. Or copy the skill folder (.codex/skills/roadmap-with-file in catlog22/Claude-Code-Workflow) into .agents/skills/roadmap-with-file in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/roadmap-with-file, .gemini/skills/roadmap-with-file, .github/skills/roadmap-with-file and .opencode/skills/roadmap-with-file in your project.
SKILL.md names no scripts, command-line tools or credentials: Roadmap With File is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Roadmap With File is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 7.5k tokens (SKILL.md is roughly 30k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Roadmap With File: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.
Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.