Plan Summary
- 1 installs
- Updated May 8, 2026
- consteon/web-spreadsheet-example
Compress the planner's completed implementation plan into a minimal structured summary and write it to disk.
About
Compress the confirmed implementation plan and write it to .claude/plans/<taskid>/plan<timestamp>.md.. The taskid must match the task file name from .claude/tasks/.
- Write to disk only; do not dump the summary into chat
- Never overwrite; always create a new timestamped file
Plan Summary by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,750 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/consteon/web-spreadsheet-example --skill plan-summaryAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | May 8, 2026 |
| Repository | consteon/web-spreadsheet-example ↗ |
What it does
Compress the planner's completed implementation plan into a minimal structured summary and write it to disk.
Files
Compress the confirmed implementation plan and write it to .claude/plans/<task-id>/plan-<timestamp>.md. The task-id must match the task file name from .claude/tasks/. The timestamp must be in YYYYMMDD-HHMMSS format generated at the time of writing. Never overwrite existing files. Omit everything that is not actionable or decision-relevant for the coder.
Plan Summary Format
1. Goal — One sentence: what this task is implementing 2. File Changes — Every file to create or modify with exact paths and content or diff 3. Raw SQL — If schema is affected, generate the full migration SQL. Include CREATE, ALTER, or DROP statements with exact column names, types, constraints, and indexes. Omit if schema is not affected. 4. Checklist — Ordered, bite-sized implementation todos the coder can tick off 5. Risks — Only unresolved risks the coder must be aware of 6. Blockers — Any BLOCKING: items that must be resolved before implementation can start
Rules
- Write to disk only. Do not dump the summary into chat. The file is the output.
- Never overwrite. Always create a new timestamped file. Previous plans are history, keep them.
- Latest wins. The coder agent always reads the most recent file by timestamp in the task folder.
- Task ID must match the task file name from
.claude/tasks/. Never invent or guess it. - No full context dumps. Do not repeat the full conversation or planning discussion.
- No placeholders. Every field must be filled with real content or omitted entirely.
- Checklist must be immediately actionable. Every item is something the coder can execute without further clarification.
Related skills
TddFollow test-driven development with a strict red-green-refactor loop when creating reliable features or fixing bugs.544k196k
Test Driven DevelopmentEnforce writing failing tests before any production implementation code.181k264kQaRun conversational QA sessions that turn user-reported bugs into well-written, domain-aware GitHub issues without manual ticket writing.179k196kMigrate To ShoehornAutomatically update TypeScript test files that rely on unsafe `as` type assertions by replacing them with type-safe partial objects from @total-typescript/shoehorn.164k196k
Webapp TestingVerify frontend behavior, debug UI issues, capture screenshots, and inspect logs of a running local web application using Playwright.123k165k
Playwright CliRun browser automation, generate element snapshots, inspect DOM attributes, and execute Playwright tests from the terminal.102k12.3k