How this skill is triggered — by the user, by Claude, or both
Slash command
/pasture:architect-handoffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- BEGIN GENERATED FROM pasture schema -->
Command: pasture:architect:handoff — Create handoff document and transfer to supervisor
-> Full workflow in PROCESS.md <- Phase 7
[arch-handoff-link-proposal]
[arch-handoff-spawn-supervisor]
[arch-handoff-supervisor-not-idle]
[arch-handoff-no-impl-tasks]
Plan ratified and user has approved proceeding with implementation.
Storage: the handoff is authored directly in the HANDOFF Beads task body (no filesystem path; the task body IS the handoff).
# Handoff: Architect → Supervisor
## Supervisor Startup
1. Call `Skill(/pasture:supervisor)` to load your role instructions
2. Spawn ephemeral Explore subagents via Task tool when codebase exploration is needed
3. Read the RATIFIED PROPOSAL and URD with `bd show` commands below
4. Every vertical slice MUST have leaf tasks — any number, named after the real work units (the L1 types / L2 tests / L3 impl triple is only illustrative)
## References
- REQUEST: <request-task-id>
- URD: <urd-task-id> (read with `bd show <urd-id>`)
- RATIFIED PROPOSAL: <ratified-proposal-id> (read with `bd show <proposal-id>`)
## Summary
<1-2 sentence summary of what needs to be implemented>
## Key Files
<list main files to be created/modified from the ratified plan>
## Validation Checklist
<validation checklist from the ratified proposal>
## BDD Acceptance Criteria
<Given/When/Then criteria from the ratified plan>
## Implementation Notes
<any special considerations, known risks, or constraints>
Create the HANDOFF Beads task — its body IS the handoff document (use the template above):
bd create --type=task --priority=2 \
--title="HANDOFF: Architect → Supervisor for REQUEST" \
--description="---
references:
request: <request-task-id>
urd: <urd-task-id>
proposal: <ratified-proposal-id>
---
# Handoff: Architect → Supervisor
<full handoff body per the template above>" \
--add-label "pasture:p7-plan:s7-handoff"
bd dep add <request-id> --blocked-by <handoff-id>
Launch the supervisor as an Opus teammate via TeamCreate (the IMPL_PLAN phase runs as an Agent Team, not aura-swarm):
TeamCreate({ team_name: "<epoch>-impl", ... }) # supervisor + workers as Opus teammates
# then assign the supervisor its task via SendMessage (see Example Prompt below)
Monitor supervisor progress:
# Check beads status
bd list --status=in_progress
A supervisor that looks idle right after spawn is usually running Explore subagents — do not shut it down pre-emptively.
CRITICAL: The SendMessage assignment MUST instruct the supervisor to invoke /pasture:supervisor as its first action. Without this, the supervisor agent starts without its role instructions and skips leaf task creation, ephemeral exploration, and other critical procedures.
Start by calling `Skill(/pasture:supervisor)` to load your role instructions.
Implement the ratified plan for <feature name>.
## Context
- REQUEST: <request-task-id>
- URD: <urd-task-id> (read with `bd show <urd-id>` for user requirements)
- RATIFIED PROPOSAL: <ratified-proposal-id>
- HANDOFF: <handoff-task-id> (the handoff body — read with `bd show <handoff-id>`)
## Summary
<1-2 sentence summary of what needs to be implemented>
## Key Files
<list main files to be created/modified from the ratified plan>
## Acceptance Criteria
<Given/When/Then criteria from the ratified plan>
## Reminders
1. Call `Skill(/pasture:supervisor)` FIRST — do not proceed without loading your role
2. Spawn ephemeral Explore subagents via Task tool when codebase exploration is needed
3. Every vertical slice MUST have leaf tasks — any number, named after the real work units (the L1/L2/L3 triple is only illustrative); a slice without leaf tasks is undecomposed
4. Read the ratified plan with `bd show <ratified-proposal-id>` and the URD with `bd show <urd-id>`
Deliver this assignment to the supervisor teammate via SendMessage after TeamCreate:
SendMessage({
to: "supervisor",
message: `Start by calling Skill(/pasture:supervisor) to load your role instructions.
Implement the ratified plan for User Authentication.
## Context
- REQUEST: project-abc
- URD: project-xyz
- RATIFIED PROPOSAL: project-prop1
- HANDOFF: project-handoff (read with bd show project-handoff)
## Summary
Add JWT-based authentication with login/logout endpoints and middleware.
## Key Files
- pkg/auth/jwt.go
- pkg/auth/middleware.go
- cmd/api/auth.go
## Acceptance Criteria
Given a valid JWT token when accessing protected routes then allow access
Given an expired token when accessing protected routes then return 401
## Reminders
1. Call Skill(/pasture:supervisor) FIRST
2. Spawn ephemeral Explore subagents via Task tool when codebase exploration is needed
3. Every slice MUST have leaf tasks (any number; L1/L2/L3 is only illustrative)
4. Read ratified plan: bd show project-prop1 and URD: bd show project-xyz`,
summary: "IMPL_PLAN assignment with Beads context"
})
Skill(/pasture:supervisor), the Beads task IDs, and bd show commands to fetch full requirements).aura-swarm for the IMPL_PLAN phase; aura-swarm remains available for worktree-isolated epics, but the default handoff uses TeamCreate.aura-swarm for the IMPL_PLAN phase — use TeamCreate with an Opus supervisorThis handoff (h1: Architect → Supervisor) also occurs after FOLLOWUP_PROPOSAL is ratified. In follow-up context:
npx claudepluginhub dayvidpham/aura-plugins --plugin pastureGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.