# to-jaan-roadmap-add

> [Internal] Add a task to the jaan.to development roadmap.
For jaan.to project maintenance, not end-user use.
Maps to: to-jaan-roadmap-add

- Author: Parhum Khoshbakht
- Repository: parhumm/jaan-to
- Version: 20260131203156
- Stars: 1
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/parhumm/jaan-to
- Web: https://mule.run/skillshub/@@parhumm/jaan-to~to-jaan-roadmap-add:20260131203156

---

---
name: to-jaan-roadmap-add
description: |
  [Internal] Add a task to the jaan.to development roadmap.
  For jaan.to project maintenance, not end-user use.
  Maps to: to-jaan-roadmap-add
allowed-tools: Read, Glob, Grep, Write(jaan-to/**)
argument-hint: [task-description]
---

# to-jaan-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-to/learn/to-jaan-roadmap-add.learn.md` - Past lessons (loaded in Pre-Execution)

## Input

**Task**: $ARGUMENTS

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

---

## Pre-Execution: Apply Past Lessons

**MANDATORY FIRST ACTION** — Before any other step, use the Read tool to read:
`jaan-to/learn/to-jaan-roadmap-add.learn.md`

If the file exists, apply its lessons throughout this execution:
- Add questions from "Better Questions"
- Note edge cases from "Edge Cases"
- Follow improvements from "Workflow"
- Avoid items in "Common Mistakes"

If the file does not exist, continue without it.

---

# 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:
```markdown
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

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

## Step 8: Confirm

```markdown
Task Added

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

Push to remote? [y/n]
```

---

## Error Handling

### No Description
> "No task description. Usage: `/to-jaan-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