Token导航 LogoToken导航

Agent Skill · 研究检索

roadmap-with-file(带文件的路线图)

roadmap-with-file 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

roadmap-with-file 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 45,077。

总安装 873周安装 36GitHub Stars 1,924下载 285核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:roadmap-with-file(带文件的路线图)
来源仓库:https://github.com/catlog22/claude-code-workflow
仓库路径:skills/roadmap-with-file
安装命令:
npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-with-file
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-with-file

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于基于文件内容生成或分析路线图,支持结构化数据处理。适合将 Markdown 或其他格式文档转化为可视化路径。通过 npx 命令从 claude-code-workflow 仓库安装,操作标准化。需确认是否要求特定文件命名规则或目录结构。

roadmap-with-file 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/roadmap-with-file

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

roadmap-with-file 怎么安装?

在终端执行 npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-with-file。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

roadmap-with-file 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

roadmap-with-file 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-with-file 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

roadmap-with-file 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

roadmap-with-file 用的人多吗?

公开数据是累计安装 873 次,近一周安装 36 次,下载 285 次,GitHub 1,924 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

roadmap-with-file 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 1,924 星,维护活跃度相对可查。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
roadmap-with-file

带文件的路线图 · 本页

8731,924执行命令未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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

$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.

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).

const result = wait_agent({
  targets: [agentId],
  timeout_ms: 600000  // 10 minutes
})

if (result.timed_out) {
  // Handle timeout - can use assign_task to prompt completion
}

assign_task

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

assign_task({
  target: agentId,
  items: [{ type: "text", text: `
## CLARIFICATION ANSWERS
${answers}

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

close_agent

Clean up subagent resources (irreversible).

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-{slug}-{date}/
└── 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

# Requirement Roadmap

**Session**: RMAP-{slug}-{date}
**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

{
  "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-{slug}-{date}",
      "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

# 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

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-${slug}-${dateStr}`
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

  1. 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 choice
  2. Strategy 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} `
  3. Initialize roadmap.md ` 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)

// 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({ targets: [exploreAgentId], timeout_ms: 120000 })

close_agent({ target: exploreAgentId })

if (exploreResult.status[exploreAgentId].completed) { codebaseContext = exploreResult.status[exploreAgentId].completed } }


1. **Execute Decomposition Agent** `` 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({targets: [decompositionAgentId], timeout_ms: 300000 // 5 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:
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) `` // 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 = ` ``

### Round ${round} - ${getUtc8ISOString()}

**User Feedback**: ${feedback} **Changes Made**: ${changesMade} **Decision**: ${decisionRecord} **Status**: ${approved? 'approved': 'continue iteration'} ` // Append to Iteration History section in roadmap.md}
  1. Finalize Iteration History
// 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 ## Roadmap Complete - **Session**: RMAP-{slug}-{date} - **Strategy**: {progressive|direct} - **Issues Created**: {count} across {waves} waves - **Roadmap**:.workflow/.roadmap/RMAP-{slug}-{date}/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) ` // 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

平台分布

Codex

36.33%
按下载量换算104

Claude

26.78%
按下载量换算76

Cursor

19.69%
按下载量换算56

Gemini CLI

9.8%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/catlog22/claude-code-workflow --skill roadmap-with-file 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills