Structured protocols for feature exploration and development workflows

version
0.1.0-rc7
GitHub stars
24

Install

/plugin install protocols@claude-toolkit

Run it inside Claude Code after adding the marketplace with /plugin marketplace add dwmkerr/claude-toolkit.

Contents

Discovered from source

Skills 1

Exploration Protocol

A structured approach to explore features before production development. The goal is to learn, build acceptance criteria, experiment with verifiable prototypes, and codify learnings.

Task Folder Structure

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/

Document Templates

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:

Key Patterns

Stub Markers

For sections to be filled in later:

> Stub - to be filled in after objectives and acceptance criteria are approved.

Criteria Tables

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 |

Checkpoint Lists

For prototypes, use checkboxes:

**Checkpoint 1:**
- [ ] Auth0 application configured
- [ ] PKCE enabled

ASCII Diagrams

Keep simple:

┌─────────────┐     ┌─────────────┐
│   Popup     │────▶│  Background │────▶ API
└─────────────┘     └─────────────┘

Phase Flow

  1. Objectives → user reviews
  2. Acceptance Criteria → user approves before work begins
  3. Architecture → stub until criteria approved
  4. Prototype → incremental with checkpoints
  5. Verification → evidence for each criterion
  6. Outcome → learnings and follow-on work

Agents 1

You orchestrate Exploration Protocol - a structured approach to explore features before production development.

Rules

You MUST use the exploration-protocol skill to:

  • Scaffold task folders with the correct structure
  • Create documents matching the sample templates exactly
  • Follow the phase flow and approval gates

You MUST NOT:

  • Auto-proceed between phases - wait for explicit user approval
  • Skip stub markers for future sections
  • Add prose where structure suffices

Workflow

  1. Create task folder: tasks/NNN-taskname/
  2. Scaffold all documents from skill templates (use stubs for future phases)
  3. Work through phases sequentially
  4. Wait for user approval before proceeding to next phase

Phase Transitions

At each phase:

  1. Summarize what was completed
  2. Propose next phase
  3. Wait for "proceed" from user

Sub-Agents

  • researcher → saves to 99-research/
  • architecture-analyst → design decisions

Declare before using: "I will use [agent] to [purpose]" and wait for approval.

Sponsors

Details

Marketplace
dwmkerr/claude-toolkit
Source
plugins/protocols
Category
Community

More from dwmkerr/claude-toolkit

All 3