plan

Stratified plan for a Trabuco-project change

This skill is the explicit gate version of stratified planning: you invoke it deliberately when you want a plan as a reviewable artifact before any code changes. The same shape is also produced ambiently by the trabuco-planner subagent when CLAUDE.md's delegation rule fires — this skill is for cases where you want to drive the gate yourself.

What you'll get

A markdown plan in canonical Trabuco-stratified shape:

# Plan: <task>

## Stage 1 — Model
- Files added/modified
**Validate:** `mvn -pl Model install`

## Stage 2 — Jobs (or whichever Layer-1 contract module applies)
...

## Stage 3 — SQLDatastore (or NoSQL)
...

(continues through layers present in this project)

## Final verification
- mvn install across the reactor
- trabuco doctor reports clean

For non-trivial features (3+ stages), the plan is also saved at .trabuco/plans/<date>-<slug>.md so the PR description can reference it and reviewers can compare diff to plan.

Flow

1. Confirm the project shape. Run mcp__trabuco__get_project_info (or cat .trabuco.json | jq .modules if MCP isn't available). If the user is not in a Trabuco project, instruct them to either cd in or run trabuco init first — stratified planning doesn't apply outside Trabuco's hierarchy.

2. Delegate to the trabuco-planner subagent. The persona owns the plan-production logic: archetype detection (additive feature / job feature / event feature / rename / bug fix / single-module / migration-only), per-stage validate commands, depends-on rationale, anti-pattern avoidance.

   Invoke as: ask the main agent to spawn @trabuco-planner with the user's task description. The planner reads .trabuco.json, picks the archetype, and produces the plan.

3. Render the plan for review. Show it in chat. Ask:

   📋 Plan ready. Approve to execute, request changes, or cancel?
   

4. On approval, hand off to the main agent for execution. The main agent works through the stages in order, running each Validate: command before proceeding to the next stage.