AGENT SKILL

copilot-flow

AI collaboration workflow plugin - Implements automated collaborative development process between Claude and Copilot through structured 5-stage workflow

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
copilot-flow
license
MIT
description
AI collaboration workflow plugin - Implements automated collaborative development process between Claude and Copilot through structured 5-stage workflow

02 资源文件 1

03 SKILL.md 正文

Copilot Flow Integration

When to use this skill:

  • When you need a structured AI-assisted development workflow
  • When you want to leverage both Claude and Copilot's strengths
  • When you require end-to-end task management from analysis to delivery

Triggering conditions:

  • When user mentions "請 Copilot 協助" (Please ask Copilot to assist)
  • When user says "詢問 Copilot" (Ask Copilot)
  • When user requests "執行 copilot-flow" (Execute copilot-flow)
  • When user starts with "copilot-flow:" or "c-flow:" prefix

Core Features

This skill orchestrates a complete 5-stage AI collaboration workflow:

  1. Analyze (Claude) - Requirements analysis and structuring
  2. Design (Copilot) - Architecture design and planning
  3. Implement (Claude) - Code implementation based on design
  4. Review (Copilot) - Code quality assessment
  5. Deliver (Claude) - Final integration and documentation

Workflow Commands

The workflow is managed through specialized slash commands in the /commands directory:

/copilot-flow:analyze [task description]

  • Executes the analysis phase
  • Claude analyzes requirements and prepares structured prompts
  • Output: analysis-result.md

/copilot-flow:design [goals]

  • Executes the design phase using Copilot MCP
  • Creates architecture design based on analysis
  • Output: architecture-design.md

/copilot-flow:implement [target]

  • Executes implementation phase
  • Claude implements code following Copilot's design
  • Output: Source code files and implementation-report.md

/copilot-flow:review [scope]

  • Executes review phase using Copilot MCP
  • Professional code review with focus areas
  • Output: code-review-report.md

/copilot-flow:deliver [objectives]

  • Executes final delivery phase
  • Claude integrates all results and documentation
  • Output: Complete delivery package

Usage Patterns

Full Workflow Execution

For complete task execution, use the workflow orchestrator:

執行 copilot-flow 實現用戶認證系統

This will:

  1. Show preview of all stages
  2. Wait for confirmation
  3. Execute each stage in sequence
  4. Manage state between stages
  5. Provide final delivery package

Individual Stage Execution

Execute specific stages independently:

/copilot-flow:analyze 分析現有代碼庫並提出改進建議
/copilot-flow:review 審查 auth.js 檔案的安全性
/copilot-flow:implement 根據設計文檔實現 API 端點

State Management

The workflow maintains state through:

  • .claude/workflow-state.json - Current stage and progress
  • Stage output files - Results from each phase
  • claude-mem integration - Complete interaction history

AI Model Collaboration

Claude Responsibilities

  • Requirements analysis and structuring
  • Code implementation and modifications
  • Final integration and delivery
  • File system operations

Copilot Responsibilities (via MCP)

  • Architecture design recommendations
  • Code quality review and feedback
  • Security and performance assessment
  • Best practices guidance

Example Workflow

User Request

執行 copilot-flow 實現一個 REST API 進行用戶認證,支持 JWT token

Workflow Execution

  1. Preview Mode - Shows planned stages and estimated time
  2. Analysis - Claude breaks down requirements
  3. Design - Copilot suggests architecture
  4. Implementation - Claude writes code
  5. Review - Copilot reviews implementation
  6. Delivery - Claude prepares final package

Outputs

  • analysis-result.md - Structured requirements
  • architecture-design.md - System design
  • Source code files - Implementation
  • code-review-report.md - Quality assessment
  • delivery/ - Complete package with docs

Best Practices

Do

  • Start with clear requirements
  • Let the workflow handle stage transitions
  • Review each stage output before proceeding
  • Use full workflow for complex tasks
  • Execute individual stages for specific needs

Don't

  • Skip stages in full workflow mode
  • Modify intermediate files manually
  • Run stages out of sequence
  • Ignore review recommendations

Error Recovery

If workflow is interrupted:

  1. Check .claude/workflow-state.json for current state
  2. Resume from last completed stage
  3. Or restart from specific stage
  4. All progress is preserved

Integration with Other Skills

  • copilot-mcp-server: Used internally by design and review stages
  • claude-mem: Records all workflow interactions
  • File system tools: Used by Claude for implementation

Keywords

AI collaboration, workflow, automation, Claude, Copilot, structured development, end-to-end, project management, code review, architecture design

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6