mxa-plan
Turns an intent into a spec before anything is built: the problem, the scope, the approach, the riskiest assumptions, the tasks and what success looks like. Then it revises the spec as the build proves parts of it wrong.
- Asks questions before it writes, because the questioning is where the thinking happens.
- Writes the spec as the one durable document the rest of the work is generated from.
- Names the riskiest assumptions first, so the build tests them early rather than discovering them late.
- Hands the tasks to the tracker rather than keeping its own list, so there is one place work lives.
- Rewrites the spec when the build contradicts it, rather than leaving a document nobody trusts.
What is inside
Instructions. Nothing here runs on its own: the judgement is the skill.
- Evals
- 3
Works with
The outside tools and connectors this skill drives.
- Markdown specs kept in the repo· our default
- Spec Kit
- exported to the issue tracker
The first is what we reach for on our own projects. A project that already uses one of the others keeps it, and the skill works with that instead.