mgw:ask missing capability context — does not read command definitions or live PR/milestone state

[snipcodeit]

Problem

`mgw:ask` gathers project context (milestone, issues, active state, recent git diff) but it does NOT read the MGW command definitions or fetch live GitHub state. The classification agent has no awareness of what commands exist or how they work, and no PR context.

This means `mgw:ask` cannot accurately classify questions like:

• "Does mgw:ask have feature X?"
• "Does mgw:run handle edge case Y?"
• "Is there a command that does Z?"

It also misses live PR context and relies entirely on `.mgw/project.json` for milestone data — if that file is absent or stale, milestone context is empty.

What mgw:ask DOES gather (confirmed in commands/ask.md)

• `.mgw/project.json` — milestone + issue list with titles, stages, labels, scopes
• `.mgw/active/*.json` — active issue pipeline state
• `git diff HEAD --stat` — recent uncommitted changes (stat only)
• `gh issue view` bodies — full GitHub issue bodies for current milestone issues

What mgw:ask does NOT gather (gaps)

Missing	Impact
`commands/*.md` front matter	Cannot answer questions about MGW capabilities
Open PRs via `gh pr list`	No PR context for classification
Live milestones via GitHub API	Falls back to stale/missing project.json

Proposed Fix

Add a new step `load_capability_context` to `ask.md` (between `load_project_context` and `load_active_state`):

1. Extract `name:` and `description:` from each `commands/*.md` front matter → `$COMMAND_SURFACE`
2. Fetch open PRs via `gh pr list --json number,title,headRefName` → `$PR_CONTEXT`
3. Fetch live milestones via `gh api repos/{owner}/{repo}/milestones` → `$MILESTONE_LIST`

Inject all three into a `<mgw_capabilities>` block in the agent prompt.

No new files required. The front matter fields (`name:`, `description:`) are consistently structured across all command files — clean extraction targets with minimal token cost.

Acceptance Criteria

• `mgw:ask` agent prompt includes a compact command capability index (name + description from each `commands/*.md`)
• `mgw:ask` fetches open PRs and includes them in agent context
• `mgw:ask` fetches live GitHub milestones as a fallback when project.json is absent
• Classification agent can accurately answer capability questions about MGW commands
• No regression on existing classification behavior (issue/active-state context unchanged)

[snipcodeit]

MGW · work-starting · 2026-03-02T03:00:00Z
Milestone: v3.5 — Foundation Hardening

Work Starting

Route	gsd:quick — Single-file change, well-scoped, no new files required
Scope	small — 1 file (commands/ask.md)
Conflicts	None — no other in-flight work touches ask.md

Work begins on branch issue/144-mgw-ask-capability-context.

Affected Files

• commands/ask.md — add load_capability_context step and extend agent prompt

[snipcodeit]

MGW · execution-complete · 2026-03-02T03:02:58Z
Milestone: v3.5 — Foundation Hardening

Execution Complete

1 atomic commit on branch issue/144-mgw-ask-capability-context.

Changes: 3 files changed, 126 insertions(+)

bf6d24f feat(ask): add load_capability_context step — command surface, open PRs, live milestones (#144)

Preparing pull request.

[snipcodeit]

MGW · pr-ready · 2026-03-02T03:03:26Z
Milestone: v3.5 — Foundation Hardening

PR Ready

PR #145 — #145

Adds load_capability_context step to mgw:ask — command surface index from front matter, open PRs, and live milestones injected into the classification agent prompt.

Testing procedures posted on the PR.
This issue will auto-close when the PR is merged.

Pipeline Summary

Stage	Status
Triage	✓
Planning	✓
Execution	✓
PR Creation	✓