Stats
Actions
Tags
From copilot-flow
Execute the first stage of the workflow - requirements analysis (executed by Claude)
How this command is triggered — by the user, by Claude, or both
Slash command
/copilot-flow:analyze [task description]copilot/This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Copilot Flow: Analyze Phase Execute the requirements analysis stage of the workflow. This stage is handled by Claude, which deeply analyzes user requirements and prepares structured prompts. ## Usage ## Execution Steps 1. **Analyze User Request** - Identify core requirements - Find implicit constraints - Confirm target users 2. **Gather Context Information** - Scan relevant files - Identify existing patterns - Check dependencies 3. **Prepare Structured Prompt** 4. **Identify Model Requirements** - Select appropriate Copilot model based on task type - R...
Execute the requirements analysis stage of the workflow. This stage is handled by Claude, which deeply analyzes user requirements and prepares structured prompts.
/copilot:analyze [task description]
Analyze User Request
Gather Context Information
Prepare Structured Prompt
# Goal
[Broad description]
# Requirements
- Requirement 1
- Requirement 2
# Example
Input: [...]
Output: [...]
# Context
Files: [...]
Functions/Classes: [...]
Constraints: [...]
Identify Model Requirements
Generate Analysis Summary
/copilot:analyze Implement a REST API for user authentication with JWT token and refresh mechanism
The output will include:
npx claudepluginhub poorgramer-zack/copilot-mcp-tool --plugin copilot-flow/phase-1Analyzes task requirements with dev/QA/UI cross-reviews and generates a detailed requirements document including goals, success criteria, estimates, risks, and questions.
/sc-planAnalyzes planning tasks or requirements, creates actionable roadmaps, and establishes strategic direction for development work.
/requirements-startStarts multi-phase requirements gathering for a feature slug from $ARGUMENTS: analyzes codebase, asks discovery questions, investigates context autonomously, and generates expert queries, producing structured docs.
/discoveryExplores project codebase and context extensively, identifies requirement gaps, then asks one focused clarifying question at a time to build a clear mental model.
/planOrchestrates multi-agent workflow across analysis and design phases to produce requirements, constraints, NFRs, data model, API contracts, and quickstart guide.
/analyzeAnalyzes project code across quality, security, performance, and architecture domains, producing severity-rated findings, actionable recommendations, metrics, and reports.