Plan

Skill nicodiansk/turbocharge/skills/plan

Opinionated engineering pipeline for Claude Code with 10 skills, 5 agents, 2 hooks. Replaces ad-hoc agent sprawl with brainstorm → story → plan → build → review → ship.

Install

npx -y skills add nicodiansk/turbocharge --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when you have stories or clear requirements that need to become an implementation plan with bite-sized tasks, exact file paths, complete code, and verification commands.

SKILL.md

2.4 KB, as published. Nobody here has run it

Create Implementation Plan

Read the requirements at $ARGUMENTS and create a detailed implementation plan.

Plan Document Header

Every plan MUST start with:

# [Feature Name] Implementation Plan

**Goal:** [One sentence]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies]

Context Gathering

Before planning, preload domain context. When dispatching the planner agent, prefix its prompt with:

@ATLAS.md (navigation index — use its Where to Look and Module Map tables before any codebase search)
@CLAUDE.md (conventions, rules, domain vocabulary)

If either file does not exist, omit the corresponding @ reference. @ references auto-read on dispatch so the subagent receives them in context; subagents do NOT inherit parent conversation history.

Token discipline: Do NOT paste file contents or summaries into the dispatch prompt — send task description, file paths, and line ranges only. The planner reads actual files in its own context. Duplicating content in the dispatch wastes tokens (same pattern as build skill).

Task Structure

Each task MUST follow this exact format:

### Task N: [Component Name]

**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py`
- Test: `tests/exact/path/to/test.py`

**Step 1: Write the failing test**
[complete test code]

**Step 2: Run test to verify it fails**
Run: `[exact command]`
Expected: FAIL with "[reason]"

**Step 3: Write minimal implementation**
[complete implementation code]

**Step 4: Run test to verify it passes**
Run: `[exact command]`
Expected: PASS

**Step 5: Commit**
`git commit -m "feat: [description]"`

Rules

Each task: 2-5 minutes of work. If longer, split it.
Exact file paths — not "somewhere in src/"
Complete code — not "add validation" or pseudocode
Exact commands with expected output
TDD always — every task starts with a failing test
DRY, YAGNI — don't plan features that aren't needed

Save

Write plan to: docs/plans/YYYY-MM-DD-<feature-name>.md

Report: plan location, number of tasks, any assumptions made.