feat(mcp): grow the prompt catalog — madtea workflows as /mcp__ slash commands #8
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #10.
Claude Code exposes MCP prompts as first-class slash commands:
/mcp__<server>__<promptname> [space-separated args](docs, verified 2026-07-06). madtea already ships 4 prompts (start branch, finish branch, file issue, +1) — this surface is confirmed-supported and underused.Candidate additions, each wrapping a golden-path workflow:
triage(rank + report the backlog),release(runbook-following release flow),reconcile(a conflicted-PR recovery path),review(fetch a PR + diff + comments for review),standup(recent activity summary).Acceptance criteria
Title, argument declarations, and completions where arguments are enumerable (repo, issue number)/mcp__<server>__<name>invocation formLanded in a later PR (2026-07-09): three new prompts —
triage(optionaltarget),review(requirednumber, steers formal verdicts toreview_create),standup(optionaldays, default 7) — plus the repo's first MCP completion support (server-wide CompletionHandler; live values fortriage.targetfrom known repos andreview.numberfrom open PRs, empty-menu degradation when uncredentialed) and generateddocs/reference/prompts.mddocumenting the/mcp__madtea__<name>invocation form.Machine-verified green: prompts/list declarations (existing 3 prompts frozen), per-prompt rendering incl. bare-invocation defaults, completion live-data + uncredentialed paths, full gate ×2, three clean adversarial review passes after a fix round.
The one criterion left open (why this stays open): "prompts appear in the Claude Code slash menu and execute with arguments" needs a live interactive session — unverifiable headless. Next interactive session on a post-release binary: type
/mcp__madtea__and confirm triage/review/standup appear and execute; then this closes. Note the correction for the record: the issue body's "madtea already implements the completion API in 4 places" referred to Cobra shell completion — there was no MCP completion code before this PR (confirmed on review).release/reconcileprompt candidates remain unbuilt — deliberately left for a future slice rather than padding this one.Confirmed new commands appear.
Verified complete against the code, not just the report. internal/mcp/prompts.go registers six prompts - start-feature, finish-branch, file-issue, plus this issue's three additions triage, review, standup - each with argument definitions, and the server declares the Completions capability with the server-wide CompletionHandler (internal/mcp/server.go:125) providing argument autocompletion. The live check recorded on this issue (2026-07-16, "Confirmed new commands appear.") covered the client-visible slash commands. All stated acceptance criteria are met. The two candidates this issue explicitly deferred (release, reconcile) are now tracked as their own leaf in #242 so the deferral survives this close; the prompts-vs-skills boundary question that came up in review is #241.