From protocols
Scaffolds task folders for structured feature exploration with templates for objectives, acceptance criteria, architecture, prototypes, and verification before production development.
npx claudepluginhub dwmkerr/claude-toolkit --plugin protocolsThis skill uses the workspace's default tool permissions.
A structured approach to explore features before production development. The goal is to learn, build acceptance criteria, experiment with verifiable prototypes, and codify learnings.
references/001-example-task/01-objectives.mdreferences/001-example-task/02-acceptance-criteria.mdreferences/001-example-task/03-architecture.mdreferences/001-example-task/04-verifiable-prototype.mdreferences/001-example-task/05-verification.mdreferences/001-example-task/06-outcome.mdskill-tests.yamlOrchestrates all code-modifying development tasks like bug fixes, enhancements, and new features using adaptive phases for analysis, specs, TDD, implementation, and verification.
Use when starting a new feature that needs thorough design exploration. This is the most comprehensive workflow: collaborative brainstorming with the user, then planning, then parallel agent development, then browser testing. Use for complex features, unclear requirements, or when the user wants to explore approaches before committing.
Share bugs, ideas, or general feedback.
A structured approach to explore features before production development. The goal is to learn, build acceptance criteria, experiment with verifiable prototypes, and codify learnings.
tasks/NNN-taskname/
├── 01-objectives.md
├── 02-acceptance-criteria.md
├── 03-architecture.md
├── 04-verifiable-prototype.md
├── 05-verification.md
├── 06-outcome.md
├── 99-research/
└── 99-findings/
You MUST read the template files in ./references/001-example-task/ before scaffolding a task folder. These templates show the exact structure and format to use:
For sections to be filled in later:
> Stub - to be filled in after objectives and acceptance criteria are approved.
Always pair criteria with verification method:
| Criterion | Verification Method |
|-----------|---------------------|
| User can log in | Manual test: complete flow, see logged-in state |
| API returns 401 on bad auth | `curl -H "Auth: bad"` shows 401 |
For prototypes, use checkboxes:
**Checkpoint 1:**
- [ ] Auth0 application configured
- [ ] PKCE enabled
Keep simple:
┌─────────────┐ ┌─────────────┐
│ Popup │────▶│ Background │────▶ API
└─────────────┘ └─────────────┘