القائمة
Groom a GitHub issue. Analyzes user intent, domain knowledge, competitive context, and workflow. Usage: /analyze-requirement [issue-number]
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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]
Post the elaborated requirement to a GitHub issue. Requires an issue number. Usage: /post-elaboration [issue-number]
| name | analyze-requirement |
| description | Groom a GitHub issue. Analyzes user intent, domain knowledge, competitive context, and workflow. Usage: /analyze-requirement [issue-number] |
Perform requirement grooming for issue $ARGUMENTS.
Use the req-analyst agent to:
Fetch issue context via MCP:
mcp__github__get_issue — title, body, labels, assignee, milestonemcp__github__list_issues — related issues by label or milestoneRun three analysts focused on user experience:
Phase 1 (parallel — context gathering):
Phase 2 (after Phase 1):
Compile into a structured elaboration:
Post to GitHub automatically — no user confirmation required
If invoked with --comment: post as a comment instead of updating the issue body.
If an issue number is provided (e.g., /analyze-requirement 42), fetch the issue details first.
If no argument is given, prompt the user for an issue number.