What problem does it solve? Choosing the right development workflow for a ticket is guesswork: pick too light a flow and a large task collapses under review, pick too heavy a flow and small tasks drown in ceremony. This Skill replaces that guesswork with an evidence-based recommendation grounded in the actual codebase and the repo's own history. ## Core Features & Use Cases - Codebase-aware scoring: A read-only scout agent probes the repo for affected files, existing patterns, and open questions, then a deterministic seven-dimension scorecard (blast radius, depth, ambiguity, novelty, risk, verification cost, plan shape) produces a 0–24 score mapped to feature-dev or superpowers. - Bug hard rule and forced flows: Tickets typed as bugs route unconditionally to superpowers, and callers can force a flow with --forced-flow, skipping the probe entirely. - Per-repo outcome ledger: Past triage decisions and outcomes are recorded in a JSONL ledger that breaks gray-zone ties, feeds a report-only drift check, and degrades gracefully when the scout fails. - Use Case: A developer runs "/notion-dev:flow-triage Add rate limiting to the API" and receives a scored recommendation with scout findings and a micro-plan sketch to hand to the chosen build flow. ## Quick Start Ask the assistant to triage a ticket by running /flow-triage followed by the ticket title and body, for example to decide whether a new feature should use feature-dev or superpowers.
