plan-template
/plan-template
The structure and rules for writing an echo plan.md (Build kickoff) from an approved spec.md. Use when running /echo:plan or generating the implementation plan. Produces a single-pass-implementable plan with a concrete Proof section.
- Author
- ybshankar010 ↗
- Repository
- echo ↗
- Licence
- Apache-2.0
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
The structure and rules for writing an echo plan.md (Build kickoff) from an approved spec.md. Use when running /echo:plan or generating the implementation plan. Produces a single-pass-implementable plan with a concrete Proof section.
Original author description
The structure and rules for writing an echo plan.md (Build kickoff) from an approved spec.md. Use when running /echo:plan or generating the implementation plan. Produces a single-pass-implementable plan with a concrete Proof section.
How it works
- Required sections
- Rules
SKILL.md preview
---
name: plan-template
description: The structure and rules for writing an echo plan.md (Build kickoff) from an approved spec.md. Use when running /echo:plan or generating the implementation plan. Produces a single-pass-implementable plan with a concrete Proof section.
---
# plan-template
A `plan.md` is the implementation plan an engineer approves before any code is
written. A good plan lets a different engineer implement it in one pass.
## Required sections
- **Header** — `Ticket:`, `Stage: Build (kickoff)`, `Derived from: spec.md`, `Status:`.
- **Files that change** — every file to create/edit, with a phrase on why.
- **Order of work** — a GitHub checkbox list, one `- [ ]` per top-level step, with the
step number kept in the text (e.g. `- [ ] 1. ...`); note which steps can run in parallel
(disjoint files). The build flow flips each box to `- [x]` as its step completes via
`echo-stage check-next`, and `/echo:status` shows the list plus a done/total count, so keep
one checkbox per step (sub-bullets stay as plain descriptive text, not counted).
- **Risks** — what could break, and the mitigation for each.
- **Proof** — the exact checks that verify the build: test commands, expected
results, manual steps. This is what the Test stage runs.
- **Definition of done** — the bar for calling this complete.
## Rules
- Name real files and real functions/utilities to reuse; do not hand-wave.
- The Proof section must be runnable, not aspirational.
- Keep the plan in sync with reality: if the build departs from it, update plan.md.
- No em dashes; lean and concrete.
- Write the prose in Simplified Technical English; load the `echo:ste-writing` skill.
Write to `.echo/artifacts/<ticket>/plan.md` (artifacts are scoped per ticket; the
`Artifacts:` line from `echo-stage status` shows the folder), then
`echo-stage set-artifact --stage plan` (the path defaults to the ticket-scoped location).
Only after I `/echo:approve` the plan does the plan-guard hook allow code edits.
Skeleton: `${CLAUDE_PLUGIN_ROOT}/templates/plan.md`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ybshankar010/echo | 90 | Apache-2.0 |
| cookys/autopilot | 96 | MIT |
Database snapshot: 13.11.2026 · package version 32ddbeff9d62 (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
- 100echo-plan
Generate plan.md (Build kickoff) from an approved spec.md, then run the critic maker-checker loop. Use when the spec gate is approved and an implementation plan is needed. - 90spec-template
The structure and rules for writing an echo spec.md (Design stage) from an approved intent.md. Use when running /echo:spec or generating the Design artifact. Applies policy while the spec is written and flags concerns. - 90plan-review-cycle
Runs a bounded specification-to-plan adversarial review cycle using the local spec-plan-reviewer agent. The approved plan is written as a section INSIDE the spec file. Use when the user wants to turn a specification into an approved implementation plan without manually passing… - 100echo
Echo framework guardrails, patterns, and best practices for AI-assisted development. Use when working with Echo projects, or when the user mentions Echo framework. Provides middleware patterns, routing, context handling, and REST API guidelines. - 100spec-conventions
This skill should be used when the user asks about "spec file format", "spec conventions", "spec vs docs", "current status section", "specification structure", "how to write a spec", "spec deliverables", or "self-contained spec". Provides conventions for writing… - 100plan-format
Use when writing, revising or repairing an implementation plan file (<name>-plan.md).