skills/parhumm/jaan-to/roadmap-add

roadmap-add

SKILL.md

roadmap-add

Add tasks to jaan.to roadmap with duplication check and proper formatting.

Context Files

  • jaan-to/roadmap.md - Current roadmap
  • jaan-to/tasks/ - Task standards
  • $JAAN_LEARN_DIR/jaan-to:roadmap-add.learn.md - Past lessons (loaded in Pre-Execution)
  • ${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md - Language resolution protocol

Input

Task: $ARGUMENTS

If no input provided, ask: "What task would you like to add to the roadmap?"


Pre-Execution Protocol

MANDATORY — Read and execute ALL steps in: ${CLAUDE_PLUGIN_ROOT}/docs/extending/pre-execution-protocol.md Skill name: roadmap-add Execute: Step 0 (Init Guard) → A (Load Lessons) → B (Resolve Template) → C (Offer Template Seeding)

Language Settings

Read and apply language protocol: ${CLAUDE_PLUGIN_ROOT}/docs/extending/language-protocol.md Override field for this skill: language_roadmap-add


PHASE 1: Analysis (Read-Only)

Step 1: Read Current Roadmap

Read jaan-to/roadmap.md to understand:

  • Current phases and their status (Done/Pending)
  • Existing tasks in each phase
  • Formatting conventions

Step 2: Duplication Check

Extract keywords from the task description and search:

grep -i "<keyword>" jaan-to/roadmap.md

If potential duplicate found:

"Similar task exists: '{existing}' in Phase {n}. Proceed anyway? [y/n/merge]"

Step 3: Phase Detection

Determine which phase the task belongs to:

Task Pattern Suggested Phase
Foundation, setup, optimization Phase 1 (Done)
Learning, docs, context Phase 2 (Done)
Development workflow, constitution Phase 3
Quick win skills (no MCP) Phase 4
MCP connectors, infrastructure Phase 5
Advanced skills (need MCP) Phase 6
Tests, polish, export Phase 7
Distribution, plugin Phase 8

Ask: "Add to Phase {suggested}? Or specify different phase (1-8)"

Step 4: Detail Check

Ask: "Does this need a detailed task doc in tasks/? [y/n]"


HARD STOP - Human Review Check

Show preview:

Ready to Add

**Phase:** {phase}
**Task:** `- [ ] {formatted task}`
**Detail doc:** {yes/no - tasks/{slug}.md}

Confirm? [y/n/edit]

Do NOT proceed without explicit approval.


PHASE 2: Write

Step 5: Format Task

Format: - [ ] {Task description}

  • If detail doc: - [ ] {Task} → [details](tasks/{slug}.md)
  • Max 5 sub-bullets for inline details

Step 6: Write to Roadmap

  1. Read current file for exact insertion point
  2. Append task to correct phase section
  3. Write using Edit tool
  4. If detail doc needed: create jaan-to/tasks/{slug}.md using template

Step 7: Auto-Commit

git add jaan-to/roadmap.md jaan-to/tasks/
git commit -m "docs(roadmap): Add {task-title} to Phase {n}"

Step 8: Confirm

Task Added

**Phase:** {n}
**Task:** - [ ] {task}
**Commit:** {hash}

Push to remote? [y/n]

Error Handling

No Description

"No task description. Usage: /jaan-to:roadmap-add Add LEARN.md files"

Duplicate Found

"Similar task '{existing}' exists. Options: proceed / merge / cancel"

Invalid Phase

"Invalid phase. Valid: 1, 2, 3, 4, 5, 6, 7, 8"


Trust Rules

  1. NEVER add without user confirmation
  2. ALWAYS check for duplicates first
  3. PRESERVE existing formatting
  4. ASK when phase is ambiguous

Skill Alignment

  • Two-phase workflow with HARD STOP for human approval
  • Single source of truth (no duplication)
  • Plugin-internal automation
  • Maintains human control over changes

Definition of Done

  • Task scope and placement confirmed with user
  • Roadmap entry added with correct phase and formatting
  • Structure rules validated (6 rules pass)
  • User approved roadmap update
Weekly Installs
2
Repository
parhumm/jaan-to
GitHub Stars
9
First Seen
Feb 23, 2026
Installed on
amp2
gemini-cli2
github-copilot2
codex2
kimi-cli2
cursor2