Milestones & Governance

Individual specifications do not exist in a vacuum. Fireskills provides high-level governance tools to organize feature slices into coherent releases, minimum viable products (MVP), and long-term evolutionary roadmaps.

The Milestone Hierarchy

Product Vision
  └── Milestone (e.g., MVP v1.0)
        ├── Spec 0001: Authentication & Workspace Setup
        ├── Spec 0002: Core Domain Resource Management
        └── Spec 0003: Stripe Subscription Billing

Milestone Governance Skills

Fireskills provides three specialized governance skills to define and maintain releases:

1. fireskill-mvp-milestone-interviewer

Focuses on defining the initial Minimum Viable Product through demonstrable, testable user states. It prevents scope creep by strictly probing what is essential for the product to function.

2. fireskill-roadmap-milestone-interviewer

Used for post-MVP evolution. After the MVP milestone is accepted, this skill structures subsequent feature requests into staged milestones with clear business impact.

3. fireskill-milestone-governor

Maintains relational integrity across specifications, milestones, and the generated specs.md roadmap projection without altering human-authored notes.

Synchronizing Milestones via CLI

To regenerate and synchronize the macro roadmap view across all specifications, run:

bun run fireskill milestones sync

This command:

1. Reads the specs (all state folders) and the backlog items.
2. Updates the derived blocks of specs.md (at the repository root) and of specs/milestones/<ID>.md, with each milestone's progress.
3. Leaves human-written text outside those blocks untouched.

External Issue Tracker Integration (ClickUp)

When managing tasks across distributed teams, specifications can link directly to external project management tools like ClickUp:

| Campo | Valor |
| --- | --- |
| ClickUp Task | https://app.clickup.com/t/86a1b2c3d |

The header field is part of the template. The clickupfy-* skills that would synchronize status and Effort with ClickUp are not part of this repository; without them the field is only a link, and the local spec is always the source of truth.