From deadfish-teams
Core deadfish invariants and protocols. Referenced by all teammates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/deadfish-teams:deadfish-coreThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
If it's real work, it exists as a Task. If it's not a Task, it's chatter.
If it's real work, it exists as a Task. If it's not a Task, it's chatter.
All structured output uses deadfish code fences. Pick the right type and emit valid YAML:
```deadfish:TYPE
key: value
nested:
- item
```
Types: SPEC, PLAN, TASK, TRACK, ADR, VERDICT, VERDICT_CRITERION, CONDUCTOR, DOCSYNC, IMPLEMENT, INTEGRATE, DIAGNOSTIC
{track}-P{N}-T{NN}
Examples: auth-P1-T01, auth-P1-T02, billing-P3-T07
npx claudepluginhub fredasterehub/deadfish-teamsInternally dispatches implementation subagents for each task during Phase 5 of the /dev workflow. Not user-facing; used by dev-implement.
Executes one implementation task from the Claude Workflow board via an 11-step protocol. Use after cw-plan or manually for autonomous coding with verification and commit.
Auto-loop execution workflow with quality gates. Use when starting any non-trivial implementation task. Provides automatic task decomposition, code implementation, testing (L1-L4), and iterative quality gates until completion. Invoke with /autoworker.