stacks-flow

Routes development tasks to the appropriate Stacks skill or workflow.

625|19|Updated Apr 26, 2022
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-flow
Source: https://github.com/stacksjs/stacks/tree/main/storage/framework/defaults/ai/skills/stacks-flow
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stacks ships more than a hundred skills, and remembering which one fits a given situation is impractical. This Skill acts as a router that maps your current task—designing, building, debugging, reviewing, or maintaining—onto the right bundled skill or flow.

Core Features & Use Cases

  • Main flow routing: Maps the idea-to-shipped path across office-hours, plan-review, new-feature, review, browse, and retro skills.
  • On-ramp guidance: Directs broken-code situations to investigation, UI work to design skills, and manual procedures to the wizard.
  • Context hygiene advice: Explains when to continue, clear, hand off, delegate to a subagent, or compact at phase boundaries.
  • Use Case: You have a vague feature idea and are unsure where to start; ask this Skill and it routes you to /stacks-office-hours for the design interview, then onward through planning and tracer-bullet implementation.

Quick Start

Ask which Stacks skill fits your current task, for example by describing that you want to turn a rough feature idea into a shipped, reviewed implementation.

Frequently Asked Questions about stacks-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Stacks skill for my task?

Describe your situation to the stacks-flow router and it maps you to the right skill. Ideas go to /stacks-office-hours, bugs go to /stacks-investigate, UI work goes to /stacks-design-taste, and upkeep goes to /stacks-codebase-design or /stacks-security-audit.

What is the main Stacks workflow from idea to shipped feature?

The main flow runs /stacks-office-hours for design, /stacks-plan-review for planning, /stacks-new-feature for tracer-bullet implementation with TDD, then /stacks-review, /stacks-browse for UI QA, and /stacks-retro to close the loop.

When should I compact a session versus clearing or handing off?

Compact only when the context stays relevant, you remain in the same harness and directory, and cheaper options fail. Continue first if possible, clear when context is irrelevant, hand off only when work travels, and use subagents for unattended tasks.

Does stacks-flow require any setup before use?

No precondition is required. Running buddy setup:ai <agent> links the bundled skills into your agent's directory, and a project-level app/Skills/<name>/SKILL.md can shadow any bundled skill.

What is the difference between subsystem skills and craft skills in Stacks?

Subsystem skills like stacks-orm and stacks-router are model-invoked references the agent finds automatically from the task. Craft skills like grilling, planning, and review shape how work happens and are routed through stacks-flow.