Flow

stacks-flow · Engineering craft · user-invoked

The router over every other skill. You will not remember a hundred and fifteen of anything, so this one names the flows instead: the main route from idea to shipped, the on-ramps that feed into it, and the vocabulary skills that run underneath. It also carries the phase-boundary tree, which is the answer to "should I keep going, clear, hand off, send a subagent, or compact?"

Inside the skill

The sections an agent reads once the skill loads.

• The main flow: idea to shipped
• On-ramps
• Codebase health
• Vocabulary underneath
• Standalone
• Precondition

Supporting files

Reference and scripts the skill reaches for on demand, rather than loading up front.

• PHASE-BOUNDARIES.md

Related skills

• Browse
• Buddy
• CMS
• Codebase design
• Design taste
• Domain modeling
• Grilling
• Guard
• Handoff
• Investigate
• New feature
• Office hours
• ORM
• Plan review
• Prototype
• Queue
• Redesign
• Registry
• REPL
• Retro
• Review
• Router
• Security audit
• Shell
• TDD
• Wizard
• Writing for agents

Using it

This one is user-invoked. It carries no model-facing description, so it costs nothing in context and only fires when you type it:

/stacks-flow

Source: stacks-flow/SKILL.md. Shadow it for one project with app/Skills/stacks-flow/SKILL.md, then re-run buddy setup:ai. See Writing your own.