Route ambiguous software tasks through Flywheel stages to the earliest useful stage.
npx skills add https://github.com/mopeyjellyfish/flywheel --skill start-mopeyjellyfish
Please help me install this Agent Skill. Skill: start Source: https://github.com/mopeyjellyfish/flywheel/tree/main/skills/start Command: npx skills add https://github.com/mopeyjellyfish/flywheel --skill start-mopeyjellyfish
Route project work through Flywheel to ensure tasks are quickly routed into the earliest useful stage, preserving context and enabling faster progression through shaping, work, review, spin, or commit.
Invoke fw:start to route the current repo task to the earliest useful Flywheel stage and surface the next action.
High-intent search queries and answers about installing and using this skill.
To route ambiguous software project tasks, invoke the fw:start entrypoint to evaluate task intent and surface the earliest useful Flywheel stage. It guides underdefined work into shaping, execution, or validation phases to maintain momentum and reduce rework.
The best way to preserve task context during software project handoffs is routing through a unified entrypoint that carries task intent forward. This approach passes relevant artifacts to downstream stages, preventing context loss and minimizing redundant setup.
You need workflow routing for software engineering tasks when a task is ambiguous or underdefined. It determines the appropriate next step by applying scope-aware routing across shaping, work, review, spin, and commit phases to keep project momentum.
The Flywheel routing flow requires no external project management dependencies. It operates by specifying a minimal entry-point SKILL.md with a name and description, optionally incorporating scripts, references, or assets to empower downstream stages.
To start software project work using the Flywheel flow, invoke fw:start. This routes the current repository task to the earliest useful stage, surfacing the immediate next action while carrying task intent and relevant artifacts forward.
Yes, you can use workflow routing for tasks across both shaping and execution phases. Scope-aware routing evaluates the task state and directs it to fw:shape, fw:work, fw:review, fw:spin, or fw:commit as needed to sustain continuous progression.
sigitpoerwoDefine a reusable Claude skill entry with YAML frontmatter in SKILL.md.
astronomerTrace downstream data lineage and assess impact across tables, DAGs, and dashboards.
AgriciDanielOrchestrate FLOW-based SEO prompts across Find, Leverage, Optimize, and Win stages.
xsw632Automate backend detection and workflow routing for Chipyard place-and-route tasks.
