prompts: release and reconcile catalog slice (deferred from the first prompt-catalog round) #242
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#242
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?
The first prompt-catalog round (#8) shipped triage, review, and standup alongside the original start-feature / finish-branch / file-issue, with argument completion via the server-wide CompletionHandler. Two candidates were explicitly deferred to a future slice rather than dropped: a release prompt (walk the cadence check, the dry run, and the runbook steps) and a reconcile prompt (drive madt_orchestrate reconcile= for a conflicted PR). Recording the deferral as its own leaf so closing #8 does not lose it.
Scope: add the two prompts following internal/mcp/prompts.go's existing pattern (AddPrompt, argument completion where an argument has an enumerable domain, docs generate). Each prompt stays a thin trigger that delegates canonical detail to madt_help topics, per the boundary being written in #241.
Acceptance: both prompts registered and listed; completion works for enumerable args; conformance/prompt tests extended; reference docs regenerated. A live client check of the new slash commands can ride any interactive session (same as #8's).