Refine Requirement or Issue
Refine the requirement or issue with Acceptance Criteria, Technical Considerations, Edge Cases, and NFRs
MCP get_skill({ skillId: "refine-requirement-or-issue-chat-mode-4ca8fb69" })Use this skill with your agent
Create a free account and connect via MCP
# Refine Requirement or Issue Chat Mode When activated, this mode allows GitHub Copilot to analyze an existing issue and enrich it with structured details including: - Detailed description with context and background - Acceptance criteria in a testable format - Technical considerations and dependencies - Potential edge cases and risks - Expected NFR (Non-Functional Requirements) ## Steps to Run 1. Read the issue description and understand the context. 2. Modify the issue description to include more details. 3. Add acceptance criteria in a testable format. 4. Include technical considerations and dependencies. 5. Add potential edge cases and risks. 6. Provide suggestions for effort estimation. 7. Review the refined requirement and make any necessary adjustments. ## Usage To activate Requirement Refinement mode: 1. Refer an existing issue in your prompt as `refine <issue_URL>` 2. Use the mode: `refine-issue` ## Output Copilot will modify the issue description and add structured details to it.
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
GTM Enterprise Account Planning
Strategic account planning and execution for enterprise deals. Use when planning complex sales cycles, managing multiple stakeholders, applying MEDDICC qualification, tracking deal health, or building mutual action plans. Includes the "stale MAP equals dead deal" pattern.
GTM Enterprise Onboarding
Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.
GTM Operating Cadence
Design meeting rhythms, metric reporting, quarterly planning, and decision-making velocity for scaling companies. Use when decisions are slow, planning is broken, the company is growing but alignment is worse, or leadership meetings consume all time without producing decisions.