Menu
Post the elaborated requirement to a GitHub issue. Requires an issue number. Usage: /post-elaboration [issue-number]
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
Generate and publish release notes for an Azure DevOps sprint. Fetches work items via WIQL, classifies them, and formats structured Markdown. Usage: /generate-release-note [sprint-name]
Post previously generated release notes to Azure DevOps wiki. Requires the release note content to already be available in context. Usage: /post-release-note [sprint-name]
Post the current PR review findings as comments on a pull request. Requires a PR number. Usage: /post-review [pr-number]
Trigger a comprehensive PR review. Runs code quality, security, test coverage, and performance analysis. Usage: /review-pr [PR number or branch name]
Groom a GitHub issue. Analyzes user intent, domain knowledge, competitive context, and workflow. Usage: /analyze-requirement [issue-number]
| name | post-elaboration |
| description | Post the elaborated requirement to a GitHub issue. Requires an issue number. Usage: /post-elaboration [issue-number] |
Post the elaborated requirement to GitHub issue #$ARGUMENTS.
Do not ask for confirmation at any point. Execute all steps autonomously and proceed immediately from one step to the next.
Verify issue exists
Use mcp__github__get_issue with the given issue number to confirm it exists and retrieve its current state, title, and labels. If the issue does not exist or is already closed, stop and output a single error line — do not ask the user what to do.
Format the elaboration for GitHub
Prepare the full elaborated requirement as the issue body (or comment body if --comment flag is set)
Map verdict to a GitHub label:
| Plugin verdict | GitHub label |
|---|---|
GROOMED | groomed |
NEEDS CLARIFICATION | needs-clarification |
NEEDS DECOMPOSITION | needs-decomposition |
Post the elaboration
Default (update issue body):
Use mcp__github__update_issue with:
issue_number: the issue numberbody: the full elaborated requirementComment mode (--comment):
Use mcp__github__create_issue_comment with:
issue_number: the issue numberbody: the full elaborated requirementThen use mcp__github__add_labels_to_issue to apply the appropriate status label.
If unresolved questions exist, post each as a separate comment using mcp__github__create_issue_comment, tagging the relevant person (@creator or @product-owner).
Output result
On completion, output a single summary line:
Elaboration posted on issue #<number>: <verdict> — <N> acceptance criteria — <N> unresolved questions
If any MCP call fails, output the error and stop — do not retry or ask for input.
Note: Requires the GitHub MCP server to be connected. See
docs/mcp-config.mdfor setup.