roadmap

Defines ordered rebuild milestones with acceptance criteria for incremental implementation sessions.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/PrimeLab-Foundation/strata --skill roadmap-primelab-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/PrimeLab-Foundation/strata/tree/main/docs/roadmap
Command: npx skills add https://github.com/PrimeLab-Foundation/strata --skill roadmap-primelab-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives developers a single source of truth for the strata rebuild's build order, so every implementation session picks exactly one well-defined increment with explicit, verifiable acceptance criteria instead of guessing what to work on next. ## Core Features & Use Cases - Ordered Milestones M0–M14: Each milestone (scaffolding, parser, serializer, bindings, JSONPath, folder mode, hardening, adapters) lists concrete deliverables and a "Done when" definition of done. - Live Status Tracking: In-progress milestones carry dated status entries recording benchmark standings, CI samples, and the current frontier of work. - Kill Criteria and Gates: Milestones like M12 include explicit kill criteria and performance gates so regressions trigger a defined fallback rather than silent drift. - Use Case: At the start of a coding session on the strata C++/Python JSON library, load this roadmap to select the current increment, verify its acceptance criteria against make test, and log ambiguities to docs/decisions.md. ## Quick Start Load the roadmap skill and tell the assistant to pick the current milestone from the strata rebuild roadmap and verify its acceptance criteria before starting work.

Frequently Asked Questions about roadmap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pick which milestone to work on in the strata rebuild?

Load the roadmap at the start of every implementation session and select the current increment from the ordered milestone list. A session works on exactly one increment, and acceptance criteria are the definition of done — verify them rather than assuming them.

What are the acceptance criteria for each roadmap milestone?

Each milestone ends with the gate green (make test on both C++ and Python layers) and docs updated in the same increment. Specific "Done when" clauses pin contract tests, benchmark standings, or property laws per milestone.

Does the roadmap track in-progress milestone status?

Yes, active milestones like M11 carry dated status entries recording CI sample standings, benchmark results per platform, and the current frontier of remaining work. Completed milestones like M10 record their release date and evidence location.

What happens when a milestone hits a performance regression?

Milestones with performance risk, such as M12, define explicit kill criteria. If a canonical benchmark row regresses past its floor due to the code change, the approach is abandoned for an alternative shape that cannot perturb existing codegen.

Where do ambiguities found during a milestone get recorded?

Ambiguities encountered during implementation go to docs/decisions.md following the Precision protocol described in workflow.md. This keeps the roadmap itself stable while design questions are resolved separately.