Name: milestone.create
Author: naturelle137

Prompt file imported from naturelle137/AeroDash (.cursor/commands/milestone.create.md). Fill in {{arguments}} before use. Copyright stays with the author.

cmd: /milestone.create
role: milestone author; safety-critical roadmap
goal: GitHub-ready milestone description; roadmap intent only
forbid:
- invent strategy
- redesign sequencing
- full validation audit
- unbacked scope
terms.exact:
- Requirement: verifiable system obligation | constraint | acceptance condition
- Journey: end-to-end user | operational flow; real-use success path
- Capability: usable behavior for user | operator | dependent system
- Milestone: versioned | testable | vertical slice; real capability progression
- Coverage: explicit map Requirement|Journey -> first satisfying Milestone
- Validation Evidence: tests | analyses | simulations | reviews | demonstrations; correctness proof
input: {{arguments}}; exact parse version
input.example: /milestone.create 0.7.0
input.invalid: return only Usage: /milestone.create <version>
discover.order:
- existing milestone roadmap | planning artifacts
- existing milestone descriptions for version
- coverage mappings from Requirements + Journeys
- alignment findings + risk notes for version
- architecture constraints + validation expectations for version
discover.blocked: missing enough intent -> return only Blocked: milestone intent for <version> is not sufficiently defined. Run /milestone.plan first or provide roadmap input.
conflict.plan-vs-align:
- preserve planned intent
- apply corrective clarifications only
- no roadmap replanning
must:
- match roadmap intent for version
- measurable | testable wording
- reflect allocated Requirements + Journeys
- explicit validation expectations
- GitHub-paste-ready
heuristics:
- vertical slices > technical layers
- usable system value required
- safety-critical logic -> early explicit validation
- no big-bang integration phrasing
- deterministic | testable outcomes
- docs + validation + runtime behavior aligned to real scope
- out-of-scope excludes adjacent blur
rules:
- use provided version exactly
- reuse roadmap name + focus when present
- if name|focus absent -> derive from Purpose + Key Capabilities; no scope change
- no new capabilities
- forbid vague verbs: handle | improve | support without measurable object
- every deliverable | exit criterion -> observable | testable | reviewable
- concise | operational wording
- audience: engineers | validators | product owners
output.only: filled template below; no preamble | notes | explanations | extra sections
output.title.h: ### Title
output.title.v: <version> - <name> (<focus>)
output.objective.h: ### Objective
output.objective.v: 2-4 concise sentences; usable value | safety-critical behavior/workflow advanced | roadmap significance
output.scope.h: ### Scope
output.scope.functional.h: #### Functional Scope
output.scope.functional.v:
- <capability or user-visible/system-visible outcome>
- <capability or user-visible/system-visible outcome>
- <capability or user-visible/system-visible outcome>
output.scope.arch.h: #### Architecture Constraints
output.scope.arch.v:
- <architecture constraint | interface boundary | data integrity rule | safety constraint>
- <architecture constraint | interface boundary | data integrity rule | safety constraint>
output.scope.tooling.h: #### Engineering / Tooling
output.scope.tooling.v:
- <tooling | observability | traceability | automation | enablement item>
- <tooling | observability | traceability | automation | enablement item>
output.exit.h: ### Deliverables & Exit Criteria
output.exit.docs.h: #### Documentation
output.exit.docs.v:
- <required document | traceability update | design artifact>
- <required document | traceability update | design artifact>
output.exit.validation.h: #### Testing & Validation
output.exit.validation.v:
- <test | simulation | verification | review outcome>
- <test | simulation | verification | review outcome>
- <test | simulation | verification | review outcome>
output.exit.runtime.h: #### Runtime Behavior
output.exit.runtime.v:
- <observable runtime property | protection | deterministic behavior | failure response>
- <observable runtime property | protection | deterministic behavior | failure response>
output.oos.h: ### Out of Scope
output.oos.v:
- <adjacent excluded item>
- <adjacent excluded item>
- <adjacent excluded item>
output.signal.h: ### Success Signal
output.signal.v: blockquote; one sentence; clearest real-world completion signal
style:
- no fluff
- no roadmap analysis
- no validation matrix
- no planning recommendations
- no meta commentary
- no unexplained jargon
- concrete nouns + measurable verbs
- every bullet reviewable + verifiable

Install milestone.create and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

- `cmd`: `/milestone.create` - `role`: milestone author; safety-critical roadmap - `goal`: GitHub-ready milestone description; roadmap intent only - `forbid`: - invent strategy - redesign sequencing - full validation audit - unbacked scope - `terms.exact`: - `Requirement`: verifiable system obligation | constraint | acceptance condition - `Journey`: end-to-end user | operational flow; real-use success path - `Capability`: usable behavior for user | operator | dependent system - `Milestone`: versioned | testable | vertical slice; real capability progression - `Coverage`: explicit map `Requirement|Journey -> first satisfying Milestone` - `Validation Evidence`: tests | analyses | simulations | reviews | demonstrations; correctness proof - `input`: `{{arguments}}`; exact parse `version` - `input.example`: `/milestone.create 0.7.0` - `input.invalid`: return only `Usage: /milestone.create <version>` - `discover.order`: - existing milestone roadmap | planning artifacts - existing milestone descriptions for `version` - coverage mappings from Requirements + Journeys - alignment findings + risk notes for `version` - architecture constraints + validation expectations for `version` - `discover.blocked`: missing enough intent -> return only `Blocked: milestone intent for <version> is not sufficiently defined. Run /milestone.plan first or provide roadmap input.` - `conflict.plan-vs-align`: - preserve planned intent - apply corrective clarifications only - no roadmap replanning - `must`: - match roadmap intent for `version` - measurable | testable wording - reflect allocated Requirements + Journeys - explicit validation expectations - GitHub-paste-ready - `heuristics`: - vertical slices > technical layers - usable system value required - safety-critical logic -> early explicit validation - no big-bang integration phrasing - deterministic | testable outcomes - docs + validation + runtime behavior aligned to real scope - out-of-scope excludes adjacent blur - `rules`: - use provided version exactly - reuse roadmap name + focus when present - if name|focus absent -> derive from Purpose + Key Capabilities; no scope change - no new capabilities - forbid vague verbs: `handle` | `improve` | `support` without measurable object - every deliverable | exit criterion -> observable | testable | reviewable - concise | operational wording - audience: engineers | validators | product owners - `output.only`: filled template below; no preamble | notes | explanations | extra sections - `output.title.h`: `### Title` - `output.title.v`: `<version> - <name> (<focus>)` - `output.objective.h`: `### Objective` - `output.objective.v`: `2-4` concise sentences; usable value | safety-critical behavior/workflow advanced | roadmap significance - `output.scope.h`: `### Scope` - `output.scope.functional.h`: `#### Functional Scope` - `output.scope.functional.v`: - `<capability or user-visible/system-visible outcome>` - `<capability or user-visible/system-visible outcome>` - `<capability or user-visible/system-visible outcome>` - `output.scope.arch.h`: `#### Architecture Constraints` - `output.scope.arch.v`: - `<architecture constraint | interface boundary | data integrity rule | safety constraint>` - `<architecture constraint | interface boundary | data integrity rule | safety constraint>` - `output.scope.tooling.h`: `#### Engineering / Tooling` - `output.scope.tooling.v`: - `<tooling | observability | traceability | automation | enablement item>` - `<tooling | observability | traceability | automation | enablement item>` - `output.exit.h`: `### Deliverables & Exit Criteria` - `output.exit.docs.h`: `#### Documentation` - `output.exit.docs.v`: - `<required document | traceability update | design artifact>` - `<required document | traceability update | design artifact>` - `output.exit.validation.h`: `#### Testing & Validation` - `output.exit.validation.v`: - `<test | simulation | verification | review outcome>` - `<test | simulation | verification | review outcome>` - `<test | simulation | verification | review outcome>` - `output.exit.runtime.h`: `#### Runtime Behavior` - `output.exit.runtime.v`: - `<observable runtime property | protection | deterministic behavior | failure response>` - `<observable runtime property | protection | deterministic behavior | failure response>` - `output.oos.h`: `### Out of Scope` - `output.oos.v`: - `<adjacent excluded item>` - `<adjacent excluded item>` - `<adjacent excluded item>` - `output.signal.h`: `### Success Signal` - `output.signal.v`: blockquote; one sentence; clearest real-world completion signal - `style`: - no fluff - no roadmap analysis - no validation matrix - no planning recommendations - no meta commentary - no unexplained jargon - concrete nouns + measurable verbs - every bullet reviewable + verifiable

{ "prompt": "- `cmd`: `/milestone.create`\n- `role`: milestone author; safety-critical roadmap\n- `goal`: GitHub-ready milestone description; roadmap intent only\n- `forbid`:\n - invent strategy\n - redesign sequencing\n - full validation audit\n - unbacked scope\n- `terms.exact`:\n - `Requirement`: verifiable system obligation | constraint | acceptance condition\n - `Journey`: end-to-end user | operational flow; real-use success path\n - `Capability`: usable behavior for user | operator | dependent system\n - `Milestone`: versioned | testable | vertical slice; real capability progression\n - `Coverage`: explicit map `Requirement|Journey -> first satisfying Milestone`\n - `Validation Evidence`: tests | analyses | simulations | reviews | demonstrations; correctness proof\n- `input`: `{{arguments}}`; exact parse `version`\n- `input.example`: `/milestone.create 0.7.0`\n- `input.invalid`: return only `Usage: /milestone.create <version>`\n- `discover.order`:\n - existing milestone roadmap | planning artifacts\n - existing milestone descriptions for `version`\n - coverage mappings from Requirements + Journeys\n - alignment findings + risk notes for `version`\n - architecture constraints + validation expectations for `version`\n- `discover.blocked`: missing enough intent -> return only `Blocked: milestone intent for <version> is not sufficiently defined. Run /milestone.plan first or provide roadmap input.`\n- `conflict.plan-vs-align`:\n - preserve planned intent\n - apply corrective clarifications only\n - no roadmap replanning\n- `must`:\n - match roadmap intent for `version`\n - measurable | testable wording\n - reflect allocated Requirements + Journeys\n - explicit validation expectations\n - GitHub-paste-ready\n- `heuristics`:\n - vertical slices > technical layers\n - usable system value required\n - safety-critical logic -> early explicit validation\n - no big-bang integration phrasing\n - deterministic | testable outcomes\n - docs + validation + runtime behavior aligned to real scope\n - out-of-scope excludes adjacent blur\n- `rules`:\n - use provided version exactly\n - reuse roadmap name + focus when present\n - if name|focus absent -> derive from Purpose + Key Capabilities; no scope change\n - no new capabilities\n - forbid vague verbs: `handle` | `improve` | `support` without measurable object\n - every deliverable | exit criterion -> observable | testable | reviewable\n - concise | operational wording\n - audience: engineers | validators | product owners\n- `output.only`: filled template below; no preamble | notes | explanations | extra sections\n- `output.title.h`: `### Title`\n- `output.title.v`: `<version> - <name> (<focus>)`\n- `output.objective.h`: `### Objective`\n- `output.objective.v`: `2-4` concise sentences; usable value | safety-critical behavior/workflow advanced | roadmap significance\n- `output.scope.h`: `### Scope`\n- `output.scope.functional.h`: `#### Functional Scope`\n- `output.scope.functional.v`:\n - `<capability or user-visible/system-visible outcome>`\n - `<capability or user-visible/system-visible outcome>`\n - `<capability or user-visible/system-visible outcome>`\n- `output.scope.arch.h`: `#### Architecture Constraints`\n- `output.scope.arch.v`:\n - `<architecture constraint | interface boundary | data integrity rule | safety constraint>`\n - `<architecture constraint | interface boundary | data integrity rule | safety constraint>`\n- `output.scope.tooling.h`: `#### Engineering / Tooling`\n- `output.scope.tooling.v`:\n - `<tooling | observability | traceability | automation | enablement item>`\n - `<tooling | observability | traceability | automation | enablement item>`\n- `output.exit.h`: `### Deliverables & Exit Criteria`\n- `output.exit.docs.h`: `#### Documentation`\n- `output.exit.docs.v`:\n - `<required document | traceability update | design artifact>`\n - `<required document | traceability update | design artifact>`\n- `output.exit.validation.h`: `#### Testing & Validation`\n- `output.exit.validation.v`:\n - `<test | simulation | verification | review outcome>`\n - `<test | simulation | verification | review outcome>`\n - `<test | simulation | verification | review outcome>`\n- `output.exit.runtime.h`: `#### Runtime Behavior`\n- `output.exit.runtime.v`:\n - `<observable runtime property | protection | deterministic behavior | failure response>`\n - `<observable runtime property | protection | deterministic behavior | failure response>`\n- `output.oos.h`: `### Out of Scope`\n- `output.oos.v`:\n - `<adjacent excluded item>`\n - `<adjacent excluded item>`\n - `<adjacent excluded item>`\n- `output.signal.h`: `### Success Signal`\n- `output.signal.v`: blockquote; one sentence; clearest real-world completion signal\n- `style`:\n - no fluff\n - no roadmap analysis\n - no validation matrix\n - no planning recommendations\n - no meta commentary\n - no unexplained jargon\n - concrete nouns + measurable verbs\n - every bullet reviewable + verifiable", "variables": [ "arguments" ], "notes": "GitHub-ready milestone description; existing roadmap only Arguments: <version>.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/naturelle137/AeroDash", "path": ".cursor/commands/milestone.create.md", "ref": "78b0445e6e3f07352f76ad5fa1cbb30c09ddd47a", "url": "https://github.com/naturelle137/AeroDash/blob/78b0445e6e3f07352f76ad5fa1cbb30c09ddd47a/.cursor/commands/milestone.create.md", "key": "naturelle137/AeroDash/.cursor/commands/milestone.create.md" } } }

milestone.create

About

Install milestone.create and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews