Flow

stacks-flow · Engineering craft · user-invoked

The router over more than a hundred skills. It names the flows: 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
• ENGINEERING.md, shared Stacks adaptation rules.
• Upstream ports, the reviewed source-to-Stacks mapping.

Related skills

• Browse
• Buddy
• CMS
• Codebase design
• Design taste
• Domain modeling
• Grilling
• Guard
• Handoff
• Humanizer
• Grill with docs
• Implement
• Implement spec
• Improve codebase architecture
• Marketing
• Investigate
• New feature
• Office hours
• ORM
• Plan review
• Prototype
• Queue
• Redesign
• Registry
• REPL
• Retro
• Review
• Router
• Security audit
• Shell
• TDD
• To spec
• To tickets
• Triage
• Wayfinder
• Unslop
• 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.

Native source verification

The skill has been checked against current source and retained tests. Read its entrypoint and linked references for the actual contract; summaries here are discovery pointers. Native capabilities maps every core package and records driver evidence without claiming universal parity.