Agent skill

Roadmap With File

by catlog22 in catlog22/Claude-Code-Workflow

Strategic requirement roadmap with iterative decomposition and issue creation.

MITAuto-check passedAgent Workflows

Install Roadmap With File

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill roadmap-with-file -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow roadmap-with-file --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
roadmap-with-file
GitHub stars
2.1k
Token cost
~7.5k tokens
SKILL.md length
932 words
Files
1
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Strategic requirement roadmap with iterative decomposition and issue creation.

  • Works in 4 steps: Requirement Understanding & Strategy → Decomposition & Issue Creation → Iterative Refinement → …
  • Agent Workflows work in your project
  • SKILL.md covers Auto Mode, Usage, Subagent API Reference and Output Artifacts, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/roadmap-with-file”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Requirement Understanding & Strategy
  2. Decomposition & Issue Creation
  3. Iterative Refinement
  4. Handoff

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~7.5k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 932 words, ~7,501 tokens.

Download SKILL.mdSave it as .claude/skills/roadmap-with-file/SKILL.md (or your agent's skills folder).
name
roadmap-with-file
description
Strategic requirement roadmap with iterative decomposition and issue creation. Outputs roadmap.md (human-readable, single source) + issues.jsonl (machine-executable).
argument-hint
[-y|--yes] [-c|--continue] [-m progressive|direct|auto] "requirement description"

Auto Mode

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 Skill

Usage

bash
$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)


Subagent API Reference

spawn_agent

Create a new subagent with task assignment.

javascript
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}
`
})
wait_agent

Get results from subagent (only way to retrieve results).

javascript
const result = wait_agent({
  timeout_ms: 1800000  // 30 minutes
})

if (result.timed_out) {
  // Handle timeout via 4-step cascade: status probe → force finalize → close
}
followup_task

Assign new work to active subagent (for clarification or follow-up).

javascript
followup_task({
  target: agentId,
  message: `
## CLARIFICATION ANSWERS
${answers}

## NEXT STEP
Continue with plan generation.
`
})
close_agent

Clean up subagent resources (irreversible).

javascript
close_agent({ target: agentId })

Output Artifacts

Single Source of Truth
ArtifactPurposeConsumer
roadmap.md⭐ Human-readable strategic roadmap with all contextHuman review, csv-wave-pipeline handoff
.workflow/issues/issues.jsonlGlobal issue store (appended)csv-wave-pipeline, issue commands
Why No Separate JSON Files?
Original FileWhy RemovedWhere Content Goes
strategy-assessment.jsonDuplicates roadmap.md contentEmbedded in roadmap.md Strategy Assessment section
exploration-codebase.jsonSingle-use intermediateEmbedded in roadmap.md Codebase Context appendix

Overview

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:

  • roadmap.md: Single source of truth — strategy, roadmap, convergence, iteration history
  • Dual decomposition: Progressive (MVP→Optimized) or Direct (topological tasks)
  • External research: Web search for architecture patterns and best practices via web.run
  • Issue creation: Issues persisted to global issues.jsonl for execution pipeline
  • Progress tracking: functions.update_plan for real-time phase progress visibility
  • Decision recording: Structured decision trail with context and rationale
  • Structured handoff: Terminal gate with execution planning, issue viewing, or completion
┌─────────────────────────────────────────────────────────────────────────┐
│                    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                                           │
│                                                                          │
└─────────────────────────────────────────────────────────────────────────┘

Dual Modes

ModeStrategyBest ForDecomposition
ProgressiveMVP → Usable → Refined → OptimizedHigh uncertainty, need validation2-4 layers, each with full convergence
DirectTopological task sequenceClear requirements, confirmed techTasks with explicit inputs/outputs

Auto-selection logic:

  • ≥3 high uncertainty factors → Progressive
  • ≥3 low uncertainty factors → Direct
  • Otherwise → Ask user preference

Output Structure

.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

roadmap.md Template

markdown
# 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**: [...]

Issues JSONL Specification

Location & Format
Path: .workflow/issues/issues.jsonl
Format: JSONL (one complete JSON object per line)
Encoding: UTF-8
Mode: Append-only (new issues appended to end)
Record Schema
json
{
  "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"
  }
}
Query Interface
bash
# 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 completed

Note: Issues are tagged with wave-N in tags[] field for filtering. Use --brief for programmatic parsing.


Implementation

Session Initialization
javascript
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" }
])

Phase 1: Requirement Understanding & Strategy

Objective: Parse requirement, assess uncertainty, select decomposition strategy, initialize roadmap.md.

Steps:

  1. Parse Requirement

    • Extract: goal, constraints, stakeholders, keywords
  2. Assess Uncertainty

    javascript
    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 choice
  3. Strategy Selection (skip if -m specified or AUTO_YES)

    javascript
    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
    }
  4. Initialize roadmap.md

    javascript
    const roadmapContent = `# Requirement Roadmap

Session: ${sessionId} Requirement: ${requirement} Strategy: ${selectedMode} Status: Planning Created: ${getUtc8ISOString()}


Strategy Assessment

  • Uncertainty Level: ${uncertaintyLevel}
  • Decomposition Mode: ${selectedMode}
  • Assessment Basis: ${factorsSummary}
  • Goal: ${extractedGoal}
  • Constraints: ${extractedConstraints}
  • Stakeholders: ${extractedStakeholders}

Roadmap

To be populated after Phase 2 decomposition


Convergence Criteria Details

To be populated after Phase 2 decomposition


Risks

To be populated after Phase 2 decomposition


Iteration History

To be populated during Phase 3 refinement


Codebase Context (Optional)

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
  }
}
  1. Execute Decomposition Agent
    javascript
    const decompositionAgentId = spawn_agent({
      agent_type: "cli_roadmap_plan_agent",
      message: `

TASK ASSIGNMENT

MANDATORY FIRST STEPS (Agent Execute)
  1. Read: .workflow/project-tech.json
  2. Read: .workflow/project-guidelines.json

Roadmap Decomposition Task

Input Context
  • Requirement: ${requirement}
  • Selected Mode: ${selectedMode}
  • Session ID: ${sessionId}
  • Session Folder: ${sessionFolder}
Strategy Assessment

${JSON.stringify(strategyAssessment, null, 2)}

Codebase Context

${codebaseContext ? JSON.stringify(codebaseContext, null, 2) : 'No codebase detected - pure requirement decomposition'}


Mode-Specific Requirements

${selectedMode === 'progressive' ? `Progressive Mode:

  • 2-4 layers from MVP to full implementation
  • Each layer: id (L0-L3), name, goal, scope, excludes, convergence, risks, effort, depends_on
  • L0 (MVP) must be a self-contained closed loop with no dependencies
  • Scope: each feature belongs to exactly ONE layer (no overlap)
  • Layer names: MVP / Usable / Refined / Optimized` :

`Direct Mode:

  • Topologically-sorted task sequence
  • Each task: id (T1-Tn), title, type, scope, inputs, outputs, convergence, depends_on, parallel_group
  • Inputs must come from preceding task outputs or existing resources
  • Tasks in same parallel_group must be truly independent`}

Convergence Quality Requirements
  • criteria[]: MUST be testable (can write assertions or manual verification steps)
  • verification: MUST be executable (command, script, or explicit steps)
  • definition_of_done: MUST use business language (non-technical person can judge)

Expected Output
  1. Update ${sessionFolder}/roadmap.md with Roadmap table + Convergence sections
  2. Create issues via ccw issue create - append to .workflow/issues/issues.jsonl
Issue Format (for ccw issue create)
  • id: ISS-YYYYMMDD-NNN (auto-generated)
  • title: [LayerName] goal or [TaskType] title
  • context: Markdown with goal, scope, convergence criteria, verification, DoD
  • priority: small→4, medium→3, large→2
  • tags: ["roadmap", mode, wave-N, layer-name]
  • extended_context.notes: {session, strategy, wave, depends_on_issues}
Execution Steps
  1. Analyze requirement and build decomposition context

  2. Execute decomposition (internal reasoning)

  3. Validate records, check convergence quality

  4. For each decomposed item:

    • Run: ccw issue create --title "..." --context "..." --tags "..." --priority N
    • Record returned Issue ID
  5. Update roadmap.md with Issue ID references

  6. 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:

  • Issues created in .workflow/issues/issues.jsonl
  • roadmap.md updated with Issue references
  • No circular dependencies
  • Convergence criteria testable

Phase 3: Iterative Refinement

Objective: 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:

markdown
> **Decision**: [Description]
> - **Context**: [What triggered this]
> - **Options**: [What was considered]
> - **Chosen**: [Selected] — **Reason**: [Why]
> - **Impact**: [What changed in roadmap]

Steps:

  1. Display Current Roadmap

    • Read and display Roadmap table + key Convergence criteria
    • Show issue count and wave breakdown
  2. Feedback Loop (skip if AUTO_YES)

    javascript
    // 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 = `
Show full SKILL.md (582 more words)Show less
Round ${round} - ${getUtc8ISOString()}

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:

  • User approved OR max rounds reached
  • All changes recorded in Iteration History
  • roadmap.md reflects final state

Phase 4: Handoff

Objective: Present final roadmap, execute MANDATORY terminal gate for next step selection.

Steps:

  1. Display Summary

    markdown
    ## 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 |
  2. MANDATORY Terminal Gate (CRITICAL — MUST execute, workflow MUST NOT end without this)

    javascript
    // 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:

  • User selection executed
  • Session complete
  • All artifacts accessible

Error Handling

ErrorResolution
cli-explore-agent failsSkip code exploration, proceed with pure requirement decomposition
cli-roadmap-plan-agent failsRetry once, fallback to manual decomposition prompt
No codebaseNormal flow, skip exploration step
Web research failsContinue without external findings, rely on inline analysis
Research conflicts with planPresent as competing evidence, let user decide direction
Circular dependency detectedPrompt user, re-decompose
User timeout in feedback loopSave roadmap.md, show --continue command
Max rounds reachedForce proceed with current roadmap
Session folder conflictAppend timestamp suffix

Core Rules

  1. Start Immediately: First action is session initialization, then Phase 1 execution
  2. Single Source: All context embedded in roadmap.md, no separate JSON files
  3. Iterate on Roadmap: Use feedback rounds to refine, not recreate
  4. Testable Convergence: criteria = assertions, DoD = business language
  5. Explicit Lifecycle: Always close_agent after wait completes to free resources
  6. Planning-Only Skill: This skill ONLY produces roadmap and issues. It NEVER executes code, creates source files, or runs implementation. All code changes happen via separate execution skills after user manually triggers them
  7. Plan-Only Modifications: Interactive feedback (Phase 3) MUST only update 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 skills
  8. MANDATORY CONFIRMATION GATE: After Phase 2 decomposition completes, you MUST present the roadmap to the user and wait for confirmation (Phase 3) before proceeding to handoff. NEVER skip Phase 3 user validation

Best Practices

  1. Clear Requirements: Detailed description → better decomposition
  2. Iterate on Roadmap: Use feedback rounds to refine convergence criteria
  3. Testable Convergence: criteria = assertions, DoD = business language
  4. Use Continue Mode: Resume to iterate on existing roadmap
  5. Wave Execution: Start with wave-1 (MVP) to validate before full execution

Usage Recommendations

When to Use Roadmap vs Other Skills:

ScenarioRecommended 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

Files

Just SKILL.md in .codex/skills/roadmap-with-file of catlog22/Claude-Code-Workflow.

Open the folder on GitHubat commit 07491b0

Compare with similar skills

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.

Roadmap With File compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Roadmap With File this skillcatlog22/Claude-Code-Workflow2.1k—~7.5kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    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

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    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.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    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.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Brainstorm

    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.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Investigate

    catlog22/Claude-Code-Workflow

    Systematic debugging with Iron Law methodology. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Issue Discover

    catlog22/Claude-Code-Workflow

    Unified issue discovery and creation. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~3.3k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Roadmap With File

What does Roadmap With File do?

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.

When should I use Roadmap With File?

Roadmap With File fits situations like: agent Workflows work in your project.

How do I install Roadmap With File in Claude Code?

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.

How do I install Roadmap With File in Codex?

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.

Can I use Roadmap With File in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Roadmap With File need to run?

SKILL.md names no scripts, command-line tools or credentials: Roadmap With File is instructions for the agent only.

Does Roadmap With File access the network?

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.

Is Roadmap With File safe to install?

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.

What licence does Roadmap With File use?

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.

How many tokens does Roadmap With File use?

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.

What are the alternatives to Roadmap With File?

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.

Who maintains Roadmap With File?

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.