harivansh-afk/claude-code-vertical
1
0
Fork 0
mirror of https://github.com/harivansh-afk/claude-code-vertical.git synced 2026-04-17 02:04:09 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

plan

Browse source
This commit is contained in:
Harivansh Rathi 2026-01-19 01:53:57 -05:00
parent a95338fbf1
commit 725f536008
1 changed files with 50 additions and 81 deletions
Download patch file Download diff file Expand all files Collapse all files

131
commands/vertical-plan.md
View file

@ -1,113 +1,82 @@
--- ---
description: Check status of plans and weavers. Shows tmux sessions, weaver progress, and PRs. description: Start an interactive planning session. Design specs through Q&A, then hand off to build.
argument-hint: [plan-id] argument-hint: [description]
--- ---
# /status Command # /plan Command
Check the status of plans and weavers. Start a planning session. You become the planner agent.
## Usage ## Usage
``` ```
/status # All plans /plan
/status plan-20260119-1430 # Specific plan /plan Add user authentication with OAuth
``` ```
## Output ## What Happens
### All Plans 1. Load the planner skill from `skills/planner/SKILL.md`
2. Generate a plan ID: `plan-YYYYMMDD-HHMMSS`
3. Create plan directory: `.claude/vertical/plans/<plan-id>/`
4. Enter interactive planning mode
## Planning Flow
1. **Understand** - Ask questions until the task is crystal clear
2. **Research** - Explore the codebase, find patterns
3. **Design** - Break into specs (each = one PR)
4. **Write** - Create spec files in `specs/` directory
5. **Hand off** - Tell user to run `/build <plan-id>`
## Spec Output
Specs go to: `.claude/vertical/plans/<plan-id>/specs/`
``` ```
=== Active Tmux Sessions === 01-schema.yaml
vertical-plan-20260119-1430-orch 02-backend.yaml
vertical-plan-20260119-1430-w-01 03-frontend.yaml
vertical-plan-20260119-1430-w-02
vertical-plan-20260119-1445-orch
=== Plan Status ===
plan-20260119-1430: running
plan-20260119-1445: running
plan-20260119-1400: complete
``` ```
### Specific Plan ## Transitioning to Build
When specs are ready:
``` ```
=== Plan: plan-20260119-1430 === Specs ready. To execute:
Status: running
Started: 2026-01-19T14:35:00Z
=== Specs === /build <plan-id>
01-schema.yaml
02-backend.yaml
03-frontend.yaml
=== Weavers === To execute specific specs:
w-01 complete 01-schema.yaml https://github.com/owner/repo/pull/42
w-02 verifying 02-backend.yaml -
w-03 waiting 03-frontend.yaml -
=== Tmux Sessions === /build <plan-id> 01-schema 02-backend
vertical-plan-20260119-1430-orch running
vertical-plan-20260119-1430-w-01 done To check status:
vertical-plan-20260119-1430-w-02 running
/status <plan-id>
``` ```
## Weaver Statuses ## Multiple Planning Sessions
| Status | Meaning | You can run multiple planning sessions in parallel:
|--------|---------|
| waiting | Waiting for dependency |
| building | Implementing the spec |
| verifying | Running verification checks |
| fixing | Fixing verification failures |
| complete | PR created successfully |
| failed | Failed after max iterations |
| blocked | Dependency failed |
## Quick Commands ```
# Terminal 1
/plan Add authentication
```bash # Terminal 2
# Source helpers /plan Add payment processing
source lib/tmux.sh
# List all sessions
vertical_list_sessions
# Status for all plans
vertical_status
# Weaver status for a plan
vertical_weaver_status plan-20260119-1430
# Capture recent output from a weaver
vertical_capture_output vertical-plan-20260119-1430-w-01
# Attach to a session
vertical_attach vertical-plan-20260119-1430-w-01
``` ```
## Reading Results Each gets its own plan-id and can be built independently.
After completion: ## Resuming
```bash Planning sessions are Claude Code sessions. Resume with:
# Summary
cat .claude/vertical/plans/plan-20260119-1430/run/summary.md
# State ```
cat .claude/vertical/plans/plan-20260119-1430/run/state.json | jq claude --resume <session-id>
# Specific weaver
cat .claude/vertical/plans/plan-20260119-1430/run/weavers/w-01.json | jq
``` ```
## PRs Created The session ID is saved in `.claude/vertical/plans/<plan-id>/meta.json`.
When weavers complete, PRs are listed in:
- The summary.md file
- Each weaver's status JSON (`pr` field)
- The overall state.json (`weavers.<id>.pr`)
Merge order is indicated in summary.md for stacked PRs.