harivansh-afk/claude-code-vertical

Fork 0

mirror of https://github.com/harivansh-afk/claude-code-vertical.git synced 2026-04-15 10:05:14 +00:00

Rathi Harivansh bc2b015fff prompts iteration

2026-01-19 16:56:25 +00:00

3.2 KiB

Raw Blame History

description

argument-hint

Start an interactive planning session. Design specs through Q&A with the planner.

description

/plan Command

Start a planning session. You become the planner agent.

Usage

/plan
/plan Add user authentication with OAuth

What You Do

When /plan is invoked:

Step 1: Load Planner Skill

Read and internalize skills/planner/SKILL.md.

Step 2: Generate Plan ID

plan_id="plan-$(date +%Y%m%d-%H%M%S)"

Step 3: Create Plan Directory

mkdir -p ".claude/vertical/plans/${plan_id}/specs"
mkdir -p ".claude/vertical/plans/${plan_id}/run/weavers"

Step 4: Start Interactive Planning

Follow the planner skill phases:

Understand - Ask questions until task is crystal clear
Research - Explore codebase, find patterns
Assess Complexity - Decide if Oracle is needed
Oracle (optional) - For complex tasks, invoke Oracle
Design - Break into specs (each = one PR)
Write - Create spec YAML files
Hand off - Tell human to run /build <plan-id>

Step 5: Confirm Plan Ready

When specs are written:

════════════════════════════════════════════════════════════════
PLANNING COMPLETE: <plan-id>
════════════════════════════════════════════════════════════════

Specs created:
  .claude/vertical/plans/<plan-id>/specs/
    01-schema.yaml
    02-backend.yaml
    03-frontend.yaml

To execute:
  /build <plan-id>

To check status:
  /status <plan-id>

════════════════════════════════════════════════════════════════

When to Use Oracle

The planner will invoke Oracle for:

Trigger	Why
5+ specs needed	Complex dependency management
Unclear dependencies	Need deep analysis
Architecture decisions	Needs extended thinking
Performance/migration planning	Requires careful sequencing

Oracle runs via browser engine (10-60 minutes typical).

Spec Output Location

.claude/vertical/plans/<plan-id>/
  meta.json           # Plan metadata
  specs/
    01-schema.yaml    # First spec
    02-backend.yaml   # Second spec
    03-frontend.yaml  # Third spec

Transitioning to Build

When specs are ready, the human runs:

/build <plan-id>

This launches the orchestrator in tmux, which spawns weavers.

Multiple Planning Sessions

Run multiple planning sessions in parallel:

# Terminal 1
/plan Add authentication

# Terminal 2
/plan Add payment processing

# Terminal 3
/plan Add notification system

Each gets its own plan-id and can be built independently.

Resuming a Planning Session

Planning sessions are Claude Code sessions. Resume with:

claude --resume <session-id>

The session ID is saved in .claude/vertical/plans/<plan-id>/meta.json.

Example Interaction

Human: /plan

Claude: Starting plan: plan-20260119-143052
        What would you like to build?

3.2 KiB Raw Blame History