Agent skill
workflow
Skill orchestration - user commands vs auto-triggered
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/workflow
SKILL.md
Workflow Overview
User Commands (6)
┌─────────────────────────────────────────────────────────┐
│ "auto" → Execute all tasks autonomously │
│ "review" → Code quality check on recent changes │
│ "brainstorm" → Scan → propose → create stories │
│ "test" → npm test + browser tests on latest │
│ "audit" → Rate aspects → create stories │
│ "status" → Quick progress check │
└─────────────────────────────────────────────────────────┘
Aliases: "what next" = brainstorm
Auto-Triggered (Internal)
| Trigger | Action |
|---|---|
| Task complete | verify runs automatically |
| Every 5 tasks | checkpoint saves context |
| User says "ship" | deploy runs |
| Artifacts pile up | clean suggested |
Analysis → Stories Flow
brainstorm / audit / what next
↓
Parallel scans (6 Haiku agents)
↓
Rate aspects / Present scenarios
↓
Auto-create stories for top issues
↓
User says "auto" → Execute
Task Lifecycle
TaskCreate (from brainstorm/audit)
↓
auto picks up task
↓
Implement → Typecheck → Build
↓
verify (auto) → Browser test if UX
↓
TaskUpdate: completed
↓
checkpoint (every 5) → Next task
Quick Reference
| Want to... | Say |
|---|---|
| Work through tasks | auto |
| Check quality | review |
| Don't know what's next | brainstorm or what next |
| Run all tests | test |
| Rate the app | audit |
| See progress | status |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?