Build & Code / D07
ProPreview cut from the real Pro body
Generate an implementation checklist
Convert a feature brief into ordered engineering tasks, test cases, rollout notes, and risks.
For
Builders
Time per use
15 min
Format
.md and .skill
How to use it
- 1.Open ChatGPT or Claude.Either works. The skill is just text.
- 2.Inspect the real preview, then unlock the full file.One click; no install, no setup.
- 3.Paste it as your first message.The assistant now knows how to do this one job.
- 4.Give it your specifics, get the result.Roughly 15 min, every time you need it.
Skill filed07-generate-an-implementation-checklist.skill.md1.5 KB
Run once
Advanced
Install permanently ↓Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.
Fill the blanks first.
These fields update the skill preview and the ChatGPT/Claude buttons instantly.
IncludeWhat needs to be built or changed?
IncludeRelevant routes, components, data models, APIs, services, design system, or repo notes.
IncludeFramework, language, database, package manager, hosting, test tools, etc.
IncludeFiles to avoid, backwards compatibility, rollout limits, deadlines, or quality bar.
IncludeKnown tests, QA flow, device/browser coverage, acceptance criteria, or missing coverage.
Install as agent behavior
Permanent agent install needs the full body.
This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.
# Generate an implementation checklist
You are a senior engineer turning a feature brief into an executable checklist. I want tasks that are small enough to delegate to a human or coding agent without losing the thread.
## Inputs
Feature brief: {{feature_brief||What needs to be built or changed?}}
Existing system context: {{system_context||Relevant routes, components, data models, APIs, services, design system, or repo notes.}}
Stack: {{stack_and_environment||Framework, language, database, package manager, hosting, test tools, etc.}}
Constraints: {{constraints||Files to avoid, backwards compatibility, rollout limits, deadlines, or quality bar.}}
Test expectations: {{test_expectations||Known tests, QA flow, device/browser coverage, acceptance criteria, or missing coverage.}}
## Output
**1. Scope boundary.** What is in and out of this implementation.
**2. Preflight inspection.** Files, commands, docs, and behavior to inspect before editing.
**3. Task checklist.** Ordered tasks grouped by:
- data/contracts
- UI or API
- state and edge cases
- error handling
- tests
- docs or release notes
**4. Verification plan.** Commands to run, manual paths to test, and screenshots or logs to capture.
**5. Risk register.** The ways this could break existing behavior.
**6. Rollout notes.** Flags, migrations, monitoring, support notes, or cleanup.
## Rules
[Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]The rest is in the Pro library.
This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.
Full Pro file includes
- ✓ Input checklist
- ✓ Step-by-step workflow
- ✓ Quality bar
- ✓ Guardrails
- ✓ Output format
- ✓ Example run
- ✓ Install formats
Other things on the Build & Code shelf