protocol

name	protocol
description	Pasture protocol reference documentation — 12-phase workflow, agent roles, constraints, and coding standards. Read when you need to understand the full workflow or look up conventions.

Pasture Protocol Reference

Complete reference documentation for the Pasture 12-phase workflow system.

Documents

Core

File	Purpose
PROCESS.md	Step-by-step workflow execution (single source of truth)
AGENTS.md	Agent roles, phase ownership, and handoff procedures
CONSTRAINTS.md	Coding standards, naming conventions, and checklists
CLAUDE.md	Reusable agent directive for projects using Pasture
SKILLS.md	Complete skill reference by role and phase
README.md	Protocol overview and quick-start
schema.xml	Beads label schema (XML format)

Templates & Examples

File	Purpose
HANDOFF_TEMPLATE.md	Standardized handoff document template
HANDOFF_EXAMPLE-web-command-impl.md	Handoff example: web command implementation
HANDOFF_EXAMPLE-ingest-pipeline-impl.md	Handoff example: ingest pipeline implementation
MR_TEMPLATE.md	Reusable merge/pull request description skeleton
EXAMPLE_MR_DESCRIPTION.md	Worked merge request description example
UAT_TEMPLATE.md	User acceptance testing template
UAT_EXAMPLE.md	UAT example with demonstrative scenarios
RESEARCH_EXAMPLE-nix-openclaw-req-ure-proposal.md	Research example: Nix/OpenClaw request through proposal

Migration & Design

File	Purpose
MIGRATION_v1_to_v2.md	Migration procedure from v1 to v2 label format
user-request-revamp-v2.md	Design doc for v2 user request phase revamp

Quick Reference

12 Phases

1. REQUEST — Capture user request verbatim, classify, research, explore
2. ELICIT + URD — Requirements elicitation survey, create URD
3. PROPOSAL-N — Architect creates technical proposal
4. REVIEW — 3 axis-specific reviewers (A/B/C), binary ACCEPT/REVISE
5. Plan UAT — User acceptance test on the plan
6. RATIFY — Ratify accepted proposal, mark old as superseded
7. HANDOFF — Architect hands off to supervisor
8. IMPL_PLAN — Supervisor decomposes into vertical slices
9. SLICE-N — Workers implement slices in parallel
10. Code Review — 3 reviewers, severity tree (BLOCKER/IMPORTANT/MINOR)
11. Impl UAT — User acceptance test on the implementation
12. LANDING — Atomic commit, push, hand off

Label Format

pasture:p{phase}-{domain}:s{step}-{type}

Follow-up Lifecycle

Trigger: UAT (Phase 5 or Phase 11) produces one or more user-DEFER'd items. Review severities never feed FOLLOWUP — all review findings reach 0 before wave close. Deferrals (user- or agent-proposed) are governed by C-uat-feedback-disposition — all deferred items are raised to the user at the next user gate for confirmation.

Owner: Supervisor creates follow-up epic (label pasture:epic-followup).

Flow:

UAT (Phase 5 or 11) produces user-DEFER'd items
  → Supervisor creates FOLLOWUP epic
    → FOLLOWUP_URE (supervisor, aggregated findings as requirements)
      → FOLLOWUP_URD (supervisor, single source of truth for follow-up)
        → h6 handoff: Supervisor → Architect
          → FOLLOWUP_PROPOSAL (architect proposes fix plan)
            → Review (same 3-axis review)
              → h1 handoff: Architect → Supervisor
                → FOLLOWUP_IMPL_PLAN (supervisor decomposes)
                  → FOLLOWUP_SLICE-N (workers implement)
                    → Code Review (severity tree, same process)

User-DEFER'd UAT-item leaf tasks are adopted as children of FOLLOWUP_SLICE-N (dual-parent). No followup-of-followup — any DEFER'd items from a follow-up UAT stay on the existing follow-up epic.

Agent Roles

Role	Phases	Key Responsibility
Epoch	1-12	Master orchestrator
Architect	1-7	Specs, proposals, review coordination
Reviewer	4, 10	End-user alignment review
Supervisor	7-12	Task decomposition, worker allocation
Worker	9	Vertical slice implementation