How do I install the Create Milestone skill?

Run npx skillmds@latest add g-bastianelli/create-milestone in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Milestone safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Milestone?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Milestone free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Milestone?

g-bastianelli (@g-bastianelli) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Milestone by g-bastianelli — Agent Skill

Name: Create Milestone
Author: g-bastianelli

Create Milestone

Use to add one milestone to an existing Linear project. Defines a meaningful delivery boundary and exit evidence, reuses supplied context, and creates the complete authorized milestone. Use create-project for cascade creation or recovery.

File contents

linear-devotee:create-milestone

Agent resolution: before any subagent dispatch, read ${CLAUDE_PLUGIN_ROOT}/shared/agent-runtime-map.md and use the active runtime's name.

Find the plugin root from this skill's directory (../..) outside Claude Code. Read ../../shared/provider-selection.md and ../../shared/planning-context.md.

Voice

Read ../../persona.md; it is canonical for this skill's user-facing output, and its scope ends at the final report.

Draft the delivery boundary

Resolve the project and milestone intent from the request or current project context. Reuse an explicit selection; list projects and ask only when the destination is ambiguous. Obtain the selected project's scope, existing milestones, and related issues. A partial cascade belongs to its own recovery workflow, not this standalone operation.

REQUIRED SUB-SKILL: Use linear-devotee:create-project for cascade recovery.

Dispatch linear-devotee:milestone-drafter with PROJECT_ID, MILESTONE_HINT, PROJECT_ROOT, current raw LINEAR_CONTEXT, and any explicit parent draft. Review the proposed boundary, exit evidence, existing issue contributions, suggested new issues, and true overlaps.

Clarify decisions that change delivery scope or its completion conditions. Recommend reuse if an existing milestone already expresses the same outcome. A target date is optional; do not invent one from the project deadline, or ask for one merely to fill a slot. Proposed issue titles are planning context and are not approved issue creations or membership changes.

Approve the complete milestone

Prepare the exact name, project id, description, and nullable target date. Mint one stable client_ref and include  in the description before showing the full preview, including scope and exit evidence.

Use explicit authorization already given for this milestone and its delegated choices. If that authority is missing, ask for approval of this complete result. Apply edits before creation; never shift a date, project, or scope after the approved preview without resolving the change.

Create and verify

Call the available milestone creation operation with exactly the previewed fields. On an error or ambiguous timeout, report the provider's actual response and stop. A retry first reloads the exact marker in the selected project; reuse one match, stop on multiple matches, and create only after confirmed absence. Do not fall back to a name match or silently adjust rejected fields.

Read back the milestone and compare its name, description, project, and date with the preview. Report a discrepancy without automatically rewriting it. Finish with the milestone link, verification result, and the proposed existing/new issue work. Continue to issue creation only when the user has requested that next step; otherwise leave it as a recommendation.

REQUIRED SUB-SKILL: Use linear-devotee:create-issue for an authorized standalone issue.

Do not attach existing issues, create suggested issues, or alter project scope as an implicit side effect of creating the milestone. Never commit, push, rebase, or blindly retry a write.

---name: create-milestonedescription: Use to add one milestone to an existing Linear project. Defines a meaningful delivery boundary and exit evidence, reuses supplied context, and creates the complete authorized milestone. Use create-project for cascade creation or recovery.---# linear-devotee:create-milestone> Agent resolution: before any subagent dispatch, read `${CLAUDE_PLUGIN_ROOT}/shared/agent-runtime-map.md` and use the active runtime's name.Find the plugin root from this skill's directory (`../..`) outside Claude Code. Read`../../shared/provider-selection.md` and `../../shared/planning-context.md`.## VoiceRead `../../persona.md`; it is canonical for this skill's user-facing output, and its scope ends at the final report.## Draft the delivery boundaryResolve the project and milestone intent from the request or current project context. Reuse anexplicit selection; list projects and ask only when the destination is ambiguous. Obtain theselected project's scope, existing milestones, and related issues. A partial cascade belongs toits own recovery workflow, not this standalone operation.**REQUIRED SUB-SKILL:** Use `linear-devotee:create-project` for cascade recovery.Dispatch `linear-devotee:milestone-drafter` with `PROJECT_ID`, `MILESTONE_HINT`, `PROJECT_ROOT`,current raw `LINEAR_CONTEXT`, and any explicit parent draft. Review the proposed boundary, exitevidence, existing issue contributions, suggested new issues, and true overlaps.Clarify decisions that change delivery scope or its completion conditions. Recommend reuse ifan existing milestone already expresses the same outcome. A target date is optional; do notinvent one from the project deadline, or ask for one merely to fill a slot. Proposed issue titlesare planning context and are not approved issue creations or membership changes.## Approve the complete milestonePrepare the exact name, project id, description, and nullable target date. Mint one stable`client_ref` and include `` in the description beforeshowing the full preview, including scope and exit evidence.Use explicit authorization already given for this milestone and its delegated choices. If thatauthority is missing, ask for approval of this complete result. Apply edits before creation;never shift a date, project, or scope after the approved preview without resolving the change.## Create and verifyCall the available milestone creation operation with exactly the previewed fields. On an erroror ambiguous timeout, report the provider's actual response and stop. A retry first reloads theexact marker in the selected project; reuse one match, stop on multiple matches, and create onlyafter confirmed absence. Do not fall back to a name match or silently adjust rejected fields.Read back the milestone and compare its name, description, project, and date with the preview.Report a discrepancy without automatically rewriting it. Finish with the milestone link,verification result, and the proposed existing/new issue work. Continue to issue creation onlywhen the user has requested that next step; otherwise leave it as a recommendation.**REQUIRED SUB-SKILL:** Use `linear-devotee:create-issue` for an authorized standalone issue.Do not attach existing issues, create suggested issues, or alter project scope as an implicitside effect of creating the milestone. Never commit, push, rebase, or blindly retry a write.

Frequently asked questions