From pad
Implement following your Pad (a markdown file named `pad.md`). Use When the user instructs you to implement something, specifying pad.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pad:impl-padThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implement following your Pad (a markdown file named `pad.md` in this repository that has instructions for you) following the "Execution" section below.
Implement following your Pad (a markdown file named pad.md in this repository that has instructions for you) following the "Execution" section below.
pad.md in this repo. if you can't find or find multiple, ask the user its path and stop your work.## New section's ### Behavior subsection in the PadDocs may lie; implementations do not.
When working, you may use only the following four types of information as authoritative:
### Current sectionDocuments that describe the implementation—including specifications, design docs, and the contents of the Pad’s ## Current section—may be used only as guidance to help you understand the implementation, guidelines, or instructions.
They must never be treated as authoritative.
After reading any implementation description, you must verify that the actual implementation matches the description. If it does not, treat the description as false and ignore it.
Always watch closely to ensure the Pad entries are correct and sufficient to fulfill the instructions. If you notice any issues, stop immediately and inform the user of what needs to be corrected.
npx claudepluginhub geb-algebra/stationery --plugin padImplements approved plans from .claude/scratchpad files by reading code fully, executing phases sequentially, verifying work, and updating checkboxes.
Executes approved implementation plans with checkpoint validation, progress tracking, and stakes-based enforcement. Locates plans, verifies approval, and runs verification criteria before proceeding.
Guides implementation phase work: executes feature plans, checks code against design, and keeps docs in sync. Use for dev-lifecycle phases 5 and 7.