Milestone creation

Workflow Milestone creation

agent starscribe

tags

workflowmilestone

context

agents/starscribe/feature.create

A milestone groups features and flows into a versioned, datable release. It answers: “What ships together, and when?” Milestones are planning artifacts — they do not define requirements, they collect them.

Features and flows included in the milestone must already exist in content/.

Phase 1 — Release Identity

Ask:

1. What is the name of this release? (e.g. MVP, v1.1, Public Beta)
2. What is the target release date? (ISO format: YYYY-MM-DD)
3. What is the single sentence that describes what this release achieves for users?

Set status="planned" for future releases, status="in-progress" for the current cycle.

Phase 2 — Included Features and Flows

List every feature and flow that ships in this release.

For each candidate ask:

• Is the feature’s status ready or better? (draft features should not be included unless explicitly scoped)
• Does including this feature pull in dependencies that are not yet scoped? (check the feature’s context references)
• Is there a corresponding flow that must also ship?

Produce the final \{% includes ref="..." /%\} list.

Phase 3 — Acceptance Conditions

Ask:

• What is the definition of done for this milestone?
• Are there specific criteria (e.g. all must requirements in included features pass QA, performance benchmarks met)?
• Are there explicit non-goals — things that are intentionally deferred to the next milestone?

Write these into the prose body of the milestone document.

Phase 4 — Draft & Confirm

Present the draft for confirmation before writing. Output: content/milestones/{id}.milestone.mdoc

---

Do’s and Don’ts

Do:

• Verify all included features and flows already exist in content/ before adding them
• Check that included features have status ready or better before including them
• Define explicit acceptance conditions and non-goals for the milestone
• Set status to planned for future releases and in-progress for the current cycle
• Present the full draft for confirmation before writing

Don’t:

• Don’t include draft features unless explicitly scoped and acknowledged by the user
• Don’t define new requirements in the milestone — milestones collect, they do not define
• Don’t include features without checking their dependency chains
• Don’t create a milestone that spans unrelated concerns; split into multiple milestones instead

Definition of Done

• Draft presented to user for confirmation
• Document written as content/milestones/{id}.milestone.mdoc with correct frontmatter and root tag
• All included features and flows exist in content/
• Acceptance conditions and non-goals are documented
• All cross-references resolve to existing documents
• pnpm compile succeeds

linktag > milestone