trove-plan
/trove-plan
Implementation planning workflow. Use after brainstorm approval or for multi-step work that needs verifiable checkpoints. Use when: write a plan; implementation plan; break this down; multi-step change.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 2
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
What it does and when to use it
Implementation planning workflow. Use after brainstorm approval or for multi-step work that needs verifiable checkpoints. Use when: write a plan; implementation plan; break this down; multi-step change.
Original author description
Implementation planning workflow. Use after brainstorm approval or for multi-step work that needs verifiable checkpoints. Use when: write a plan; implementation plan; break this down; multi-step change.
How it works
- Session Init
- Throughput checkpoint
- Plan Shape
- Decision Gate: plan readiness
- Handoff
SKILL.md preview
--- name: trove-plan description: "Implementation planning workflow. Use after brainstorm approval or for multi-step work that needs verifiable checkpoints. Use when: write a plan; implementation plan; break this down; multi-step change." --- <!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills --> ## Session Init This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict. If a sibling skill in this plugin matches the request more directly, defer to it. See `AGENTS.md` (or `docs/routing.md` in the marketplace) for the per-plugin routing index. # trove-plan A plan is a sequence of verifiable checkpoints, not a wish list. ## Throughput checkpoint Before sequencing, answer four questions so the plan parallelizes safely and doesn't serialize work that's actually independent: 1. **Blocking first steps** — what must land before anything else can start? 2. **Independent workstreams** — what can proceed in parallel (disjoint files/subsystems)? 3. **Shared mutable state** — what would two parallel workstreams both write? Eliminate the sharing or serialize that part. 4. **Smallest safe decomposition** — the fewest checkpoints that each verify independently. Keep an n/a answer in the list with a one-line reason rather than dropping it. Prefer several small checkpoints over a few large ones, staying within the seven-checkpoint cap below; each must be independently verifiable (static + runtime). ## Plan Shape Create at most seven checkpoints. Each checkpoint must include: - The files or subsystem likely touched. - The observable result after the checkpoint. - The verification command or inspection needed before moving on. ## Decision Gate: plan readiness Context: Execution should start only when the checkpoints are independently verifiable. Question: Is this plan concrete enough to execute one checkpoint at a time? Options: - A. Yes - execute checkpoint 1. - B. Revise the plan. - C. Stop for missing information. Default: B, because vague checkpoints make verification meaningless. ## Handoff When the user approves the plan, route to `trove-execute-plan`. Do not execute while still drafting the plan unless the user has explicitly asked for immediate implementation and the change is narrow.
Versions
The database has no other skills named trove-plan.
Identical content appears in 3 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8b80c380e262 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100trove-autoplan
Front-door planning workflow. Take an idea and produce implementation-ready output by composing the Trove product skills (spec → user stories → release-note preview). Defers all detail to the leaf skills it calls. Use when: autoplan; turn this idea into a plan; draft an… - 100ce-plan
Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing. - 90trove-brainstorm
Feature and design brainstorming gate. Use before implementing a new feature, UI, refactor, or product change when no approved design exists. Use when: let's build; add a feature; design this; refactor this flow; brainstorm. - 90implementation-plan
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview. - 90plans
Use when multi-step work needs a structured implementation plan that preserves outcomes and constraints. Not for exploratory framing, executing the work, or running tests to learn from results. - 90implement
Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.