Command reference and workflow guide for Towline.
Provides command references and workflow guidance for Towline.
npx claudepluginhub sienklogic/towlineThis skill is limited to using the following tools:
If $ARGUMENTS contains a command name (e.g., plan, build, review, config, quick), show detailed help for just that command instead of the full reference. Match the argument against the command tables below and display only the matching section with its subcommands and flags. If the argument doesn't match any command, show the full reference.
Examples:
/dev:help plan → Show only the plan command and its flags (--assumptions, --skip-research, --gaps, add, insert, remove)/dev:help build → Show only the build command and its flags (--gaps-only, --team)/dev:help → Show the full reference belowDisplay the following reference to the user:
| Command | Description | Cost |
|---|---|---|
/dev:begin | Start a new project. Deep questioning, research, requirements, roadmap. | High (4-6 agents) |
/dev:plan <N> | Plan a phase. Research, create plans, verify before building. | Medium (2-3 agents) |
/dev:build <N> | Build a phase. Execute plans in parallel waves, verify results. | High (2-4 agents) |
/dev:review <N> | Review what was built. Automated verification + walkthrough with you. | Low (1 agent) |
| Command | Description |
|---|---|
/dev:explore [topic] | Explore ideas, think through approaches. No phase number needed. |
/dev:discuss <N> | Talk through a phase before planning. Captures decisions. |
/dev:plan <N> --assumptions | Surface Claude's assumptions before planning. Zero cost. |
/dev:plan <N> --skip-research | Plan without research phase. Faster. |
/dev:plan <N> --gaps | Create gap-closure plans from verification failures. |
/dev:plan add | Append a new phase to the roadmap. |
/dev:plan insert <N> | Insert a phase using decimal numbering. |
/dev:plan remove <N> | Remove a future phase and renumber. |
| Command | Description |
|---|---|
/dev:build <N> | Execute all plans in a phase. |
/dev:build <N> --gaps-only | Execute only gap-closure plans. |
/dev:build <N> --team | Use Agent Teams for complex inter-agent coordination. |
/dev:quick | Quick ad-hoc task with atomic commit. Low cost. |
/dev:continue | Execute the next logical step automatically. No prompts. |
| Command | Description |
|---|---|
/dev:review <N> | Verify phase + conversational UAT. |
/dev:review <N> --auto-fix | Auto-diagnose and fix verification failures. |
/dev:debug | Systematic debugging with hypothesis testing. |
/dev:scan | Analyze existing codebase (brownfield). |
| Command | Description |
|---|---|
/dev:status | Where am I? Shows progress and suggests next action. |
/dev:health | Check planning directory integrity. Find and fix corrupted state. |
/dev:pause | Save session state for later. |
/dev:resume | Pick up where you left off. |
| Command | Description |
|---|---|
/dev:milestone new | Start a new milestone cycle. |
/dev:milestone complete | Archive completed milestone. |
/dev:milestone audit | Verify milestone completion. |
/dev:milestone gaps | Create phases to close audit gaps. |
/dev:todo add|list|done | Persistent file-based todos. |
/dev:note <text>|list|promote | Zero-friction idea capture. Quick notes that persist across sessions. |
/dev:config | Configure workflow settings. |
/dev:setup | Interactive onboarding wizard for new projects. |
/dev:begin ← Start project, define requirements, create roadmap
/dev:discuss 1 ← (optional) Talk through phase details
/dev:plan 1 ← Plan the first phase
/dev:build 1 ← Build it
/dev:review 1 ← Verify it works
/dev:plan 2 ← Plan the next phase
... ← Repeat plan → build → review
/dev:milestone complete ← Archive when done
aggressive (delegate everything) | balanced | minimal (run inline)quick (skip research, ~50% cheaper) | standard | comprehensive (~2x cost).planning/STATE.md (position), .planning/ROADMAP.md (phases), .planning/config.json (settings)/dev:config to change depth, models, gates, parallelization/dev:quick for creative/visual work where structured planning adds overhead without benefit..planning/ commits can be filtered using phase branching (git.branching_strategy: phase) which squash-merges code-only changes to main./dev:explore can create seed files (.planning/seeds/) with trigger conditions. Seeds auto-inject into planning when their trigger phase is reached.Towline includes three behavioral contexts in contexts/ that adjust how Claude operates:
Skills automatically activate the appropriate context: /dev:build uses dev context, /dev:discuss uses research context, /dev:review uses review context.
───────────────────────────────────────────────────────────────
## ▶ Next Up
→ `/dev:begin` — start a new project
→ `/dev:status` — check current project status
→ `/dev:config` — configure workflow settings
→ `/dev:help <command>` — detailed help for a specific command
───────────────────────────────────────────────────────────────
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.