fp

Plugin fp from marketplace flightplan in saurabhhbansal/flightplan. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• abandon

  Retire a change that will never ship — explored and rejected, superseded, or overtaken. Records why, moves it to archive marked abandoned, and applies no delta to the living specs.

• analyze

  Consistency gate for a Flightplan change — cross-check constitution, proposal, design, delta and tasks for gaps, contradictions, untested requirements, scope creep and constitution violations before any code is written.

• archive

  Close out a verified Flightplan change — fold its spec delta into the living specs/, update product.md, and move the change folder to archive/. Keeps <SPEC_ROOT>/specs as current truth.

• atomic-tasks

  Use when breaking a plan or change into implementation tasks — how to make each task atomic, acceptance-testable and sized for a fresh context, then group them into dependency waves that can run in parallel.

• constitution

  Create or amend <SPEC_ROOT>/constitution.md — the project's non-negotiable laws (conventions, quality bar, architecture rules) that every Flightplan change is checked against.

• design

  Produce the technical design for a Flightplan change — the "how" (architecture, data model, interfaces, key decisions), validated against the constitution, plus the spec delta describing how the living specs will change.

• disciplined-debugging

  Use when a test fails, a bug appears, or behaviour is wrong — a four-phase method that finds the root cause before changing any code, instead of patching symptoms.

• implement

  Execute a Flightplan change wave by wave with TDD. Runs tasks in the main context by default and fans parallel-safe waves out to fresh fp-implementer subagents (hybrid context engineering).

• init

  Initialise Flightplan in a repo — resolve and record where artifacts live, detect whether the repo has a test harness, bootstrap the constitution and seed product.md. Run this once, before any other /fp command.

• propose

  Start a Flightplan change. Socratically clarify a rough idea until it is unambiguous, then write a proposal (why/what, v1 vs later scope) under <SPEC_ROOT>/changes/. The entry point for any new work.

• spec-clarify

  Use when turning a vague feature idea or request into a clear spec — interrogate goals, users, scope boundaries, constraints and edge cases before writing anything. Triggers during proposing/brainstorming/requirements work.

• status

  Show the state of Flightplan in this repo — active changes, their stage and track, wave/task progress, and the single next command to run. Your dashboard.

• tasks

  Decompose a Flightplan change into atomic, individually-verifiable tasks grouped into dependency waves, each sized to fit a fresh context window. The unit of execution.

• tdd-loop

  Use when implementing a task or feature that has testable behaviour — enforce the RED/GREEN/REFACTOR test-driven cycle so a failing test exists before any implementation code.

• verify-before-done

  Use before claiming a task, change or fix is complete — prove it by exercising the real behaviour and reporting results honestly, not by asserting success from a green typecheck alone.

• verify

  Prove a Flightplan change actually works by exercising the real feature end-to-end (not just unit tests), against the acceptance criteria in the proposal/delta. Gates archive.

Subagents (2)

• fp-implementer

  Executes a SINGLE Flightplan task end-to-end with TDD in an isolated, fresh context. Dispatched by /fp:implement for parallel-safe tasks within a wave. Give it one task block plus the constitution and only the spec/design sections it needs.

• fp-researcher

  Investigates an unfamiliar domain, library, API or design question and returns a concise findings brief. Dispatched by /fp:propose to de-risk a proposal. Read-only — it never edits the project.

Similar plugins