Menu
Manage GitHub Milestones for Infiquetra Objectives. Creates, lists, links, and tracks milestone progress when an Objective needs due-date rollup across one or more repos.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Route proposed Team Mimir profile behavior changes to target-owned Hermes dialogue.
Build a versioned Antigravity teammate delegation envelope and route it through the guarded agy wrapper.
Create durable Infiquetra implementation plans with issue, review, test, and deploy gates. Interrogates HOW work gets built, writes an agent-consumable plan artifact, records a plan saga, and routes to doc-review and /work. Triggers on "plan this", "how should we build this", "create a plan", "break this down", or a handoff issue ready for planning.
Coordinate a whole outcome as a durable DAG of leaf sagas. A level-triggered reconcile loop that dispatches the ready frontier to executors, harvests completion, and pages the operator only at gates and exceptions. The coordinator routes and never runs leaf work; status is derived on read. Thin coordinator verbs only — start, graph, advance, attend, resume, discover, handoff, attach — leaf work stays the native /resume, /work, /code-review, /qa.
Execute a settled Infiquetra plan to PR-ready, then own the round-N PR continuation loop. Restores and writes the work-thread saga (the primary writer), recommends an execution backend, runs risk-gated tests, calls /code-review programmatically and reads its envelope, gates hard on P0/P1 and stale reviews, and coordinates PR-open/review-request/merge under explicit confirmation — without owning deploy. Triggers on "build it", "work this plan", "execute the plan", "resume work on
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.
| name | milestones |
| description | Manage GitHub Milestones for Infiquetra Objectives. Creates, lists, links, and tracks milestone progress when an Objective needs due-date rollup across one or more repos. |
| when_to_use | Use this skill when the user wants to: Creating objectives and milestones: - "create an objective for the platform launch", "set up a new objective" - "create a milestone for this objective", "set up the v1.0 release milestone" Progress and status: - "objective progress", "milestone completion", "are we on track for the release date" Milestone management: - "when is this objective due", "list all open milestones" - "which milestones are at risk", "show upcoming deadlines" Linking issues to objectives: - "link issue #42 to the platform MVP milestone" - "assign this to the current objective" |
Manage GitHub Milestones as an optional Objective progress surface. The canonical hierarchy is still Initiative -> Objective -> work item, with Initiative and Objective represented as project fields when the board exposes them. Milestones are useful for repo-level due dates, GitHub progress rollups, and release coordination.
$INFIQUETRA_SDLC_PATH/../infiquetra-claude-plugins/plugins/mission-control/scripts/sdlc_manager.py
If $INFIQUETRA_SDLC_PATH is unset, use ~/workspace/infiquetra/infiquetra-sdlc as the default base path.
Always run the script with python3.
python3 sdlc_manager.py milestones create \
--repo infiquetra-core \
--title "Pilot: Platform Launch (2026-04-15)" \
--due-date 2026-04-15 \
--description "Validate core workflows with early adopters"
python3 sdlc_manager.py milestones list --repo infiquetra-core
python3 sdlc_manager.py milestones list --repo infiquetra-core --state all
python3 sdlc_manager.py milestones list --repo infiquetra-core --state closed
python3 sdlc_manager.py milestones progress --repo infiquetra-core --milestone 3
Progress uses GitHub's open/closed issue counts for issues linked to that milestone.
python3 sdlc_manager.py milestones link \
--repo infiquetra-core \
--issue 42 \
--milestone 3
Equivalent gh CLI:
gh issue edit 42 --repo infiquetra/infiquetra-core --milestone "Pilot: Platform Launch (2026-04-15)"
Milestone title:
{Type}: {Name} ({YYYY-MM-DD})
| Type | Example |
|---|---|
| Pilot | Pilot: Platform Launch (2026-04-15) |
| MVP | MVP: Core Integration (2026-02-28) |
| Release | Release: Olympus v1.0 (2026-05-30) |
| Program | Program: Q1 KR1 - User Adoption (2026-03-31) |
Objective field value.Example field update:
python3 sdlc_manager.py flow set-field --project operations \
--repo <repo> --number <N> \
--field Objective --option "<Objective name>"
Flag Objectives as at-risk when:
Assigned, In Review, Active, or Verify.Needs Question or equivalent state.Check progress:
python3 sdlc_manager.py milestones progress --repo <repo> --milestone <N>
For Objectives spanning multiple repositories:
An Objective is complete when:
Done, Closed, or equivalent)."Create an objective for the platform launch" -> Create the Objective field option and Outcome Scorecard doc, then create a milestone if useful.
"How's the platform launch going?"
-> Find the milestone number and run milestones progress.
"Add capability #42 to the platform-launch objective" -> Set the Objective field and link to the milestone if one exists. Add a native parent only when the Capability is a real child of an explicit Outcome proof card.
"Which objectives are at risk?" -> Run progress for each open milestone and check linked board status / WIP age.
references/objective-workflow.md - Objective lifecycle, types, sizing, and examples