plan-mode

Generates per-step implementation plans with verify clauses, dependency graphs, and slicing strategies.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/TierOne-Studio/spa-velocity --skill plan-mode-tierone-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-mode
Source: https://github.com/TierOne-Studio/spa-velocity/tree/main/.ruler/skills/plan-mode
Command: npx skills add https://github.com/TierOne-Studio/spa-velocity --skill plan-mode-tierone-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial coding tasks often fail due to hidden assumptions, scope drift, and unreviewable big-bang diffs. This Skill enforces a structured planning phase before any code is written, surfacing ambiguity, risk, and dependencies up front. ## Core Features & Use Cases - Requirements gate: Produces falsifiable acceptance criteria, non-goals, an explicit assumptions block, and anticipated failure modes before planning begins. - Structured per-step plans: Each of 3–8 steps includes verify clauses, files to touch, API impact, tests, risk notes, and a ~100 LOC slice cap. - Dependency-graph ordering and slicing strategies: Orders work bottom-up through schema, service, query hook, component, and tests, choosing vertical, risk-first, or contract-first slicing. - Use Case: Before refactoring a React feature that touches the API client, TanStack Query hooks, and components, invoke this Skill to produce a step-by-step plan with verification criteria and an ADR step for any structural decision. ## Quick Start Ask the assistant to enter plan mode and produce a step-by-step plan with verify clauses before implementing your multi-file feature or refactor.

Frequently Asked Questions about plan-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a multi-file code change before implementing it?

Use plan mode to write 3–8 steps, each with a verify clause, files to touch, API impact, tests, and risk notes. Order steps by the dependency graph, foundations first, and keep each slice near 100 lines of code.

When should I use plan mode instead of coding directly?

Use it for tasks with 3+ steps, multi-file changes, architectural decisions, or debugging with uncertain root cause. Skip it for trivial single-file edits, factual answers, or read-only investigations with obvious answers.

What is a vertical slice versus a horizontal slice in planning?

A vertical slice cuts through every layer end-to-end, from schema to service to component to test, for one narrow path. A horizontal slice completes one layer at a time; vertical slices are demoable and committable independently.

When should a plan include an architecture decision record?

Include an ADR step whenever the plan introduces a load-bearing decision such as a new state-management library, auth flow, or public API contract. The ADR is written in docs/decisions with its own verify clause.

What should I do when a plan stops working mid-implementation?

Stop and re-plan when new evidence contradicts an assumption, a test fails unexpectedly, scope expands, or the fix feels hacky. Do not keep pushing on a flawed plan.