fw

Plugin fw from marketplace hl-mp in hl/mp. Commands read from the repo's manifest — 1 month ago.

Skills (2)

• fw-brainstorm-approach

  Question cadence for structured discovery. Load when a brief is ambiguous and a spec needs to be written.

• fw-template

  Canonical spec format for agent-driven development. Load when writing or reading a spec.

Slash commands (6)

• /fw:compound

  Document a completed feature to docs/solutions/ for future agent sessions.

• /fw:draft

  Write a spec for a new feature. Conducts a brainstorm if the brief is fuzzy. Skips if the work does not warrant a spec.

• /fw:init

  One-time setup. Creates docs/specs/ and docs/solutions/, and teaches CLAUDE.md (or AGENTS.md) about the spec-driven workflow so future agents know to use it. Idempotent.

• /fw:refresh

  Refresh stale entries in docs/solutions/. Checks references, patterns, and overlap against the current codebase. Requires a scope argument (category, module, tag, or file path).

• /fw:review

  Check the current implementation against the spec. Produces findings to feed back into /plan.

• /fw:validate

  Validate a spec for completeness and ambiguity before implementation begins.

Subagents (6)

• fw-compound

  The fourth move of the spec-driven loop. Captures the knowledge accumulated during a completed feature, makes it findable, updates the project so future agents apply it, and verifies the learning will surface next time. Embodies the Compound Engineering compound step: each unit of work should make t

• fw-draft

  Produces a spec in docs/specs/ or determines that no spec is needed. Conducts a structured brainstorm if the brief is fuzzy. Skips if the work does not warrant a spec. Trigger phrases: - "write a spec for" - "draft a spec" - "create a spec for" - "spec out this feature" <example> Context: User has a

• fw-init

  One-time setup for adopting the flywheel plugin on a project. Creates docs/specs/ and docs/solutions/, and teaches the project's CLAUDE.md (or AGENTS.md) about the spec-driven workflow so agents working in the project know when to use /fw:draft, /fw:review, /fw:compound. Idempotent — safe to re-run.

• fw-refresh

  Reviews stale entries in docs/solutions/ and proposes targeted updates. Checks docs against the current codebase: missing file references, superseded patterns, conventions that have shifted, and overlap with newer solutions. Maintenance tool — keeps the knowledge store trustworthy as the codebase ev

• fw-review

  Checks whether the current implementation satisfies the spec. Produces findings that feed back into /plan. Does not suggest implementation approaches. Trigger phrases: - "review my changes against the spec" - "check implementation against spec" - "what's left from the spec" <example> Context: Implem

• fw-validate

  Validates a spec for quality before implementation begins. Catches ambiguity and gaps that would force an agent to make assumptions during implementation. Returns findings; does not rewrite the spec. Trigger phrases: - "review the spec" - "validate the spec" - "check the spec for gaps" <example> Con