granoflow-milestone-workflow

Granoflow Milestone Workflow

Use this Skill to plan and create project milestones after Project Definition prerequisites pass. It supports single create and batch create. It does not draft Milestone Work charters, create child tasks, run Analysis, or close milestones.

For creating high-quality child tasks, use granoflow-task-authoring.
For create-all-milestones then create-all-tasks, use granoflow-portfolio-orchestrator.
For charter → coordinate → integrate → close, use granoflow-milestone-coordination.

Keyword

• #milestone-workflow
• #milestone-create
• #batch-create-milestones

When To Use

• Create one milestone, or create the full planned milestone set.
• Amend the portfolio when Project Work coverage has a real gap.
• Called by granoflow-portfolio-orchestrator as the milestone-creation step.

Do not use this Skill to invent milestones when Project Work / frontend baseline gates fail. Do not use it to author task titles/descriptions or execute work.

Entry Prerequisites (Hard Gate)

Before any milestone planning or entity creation, verify all of the following. On failure, stop, return project_milestone_prerequisites_incomplete, and hand back to granoflow-project-definition. Do not create App milestones.

1. Project Work is complete, current, and App-confirmed.
2. If the project includes frontend, the confirmed Design Baseline must exist with exact prototypeId / versionId / packageSha256 readback, landscape and portrait App Shell, and successful visual_confirmation.

Frontend Detection

Treat the project as including frontend when any of these hold:

• product / platforms / supported surfaces indicate app, web, desktop, or other user-facing UI;
• Project Work already has a non-empty design_profile or prototype_template reference;
• the user explicitly states the project has frontend/UI.

Backend-only / CLI-only / library-only projects without UI skip the Design Baseline + App Shell requirement but still require complete Project Work.