Ai-Team-Producer
Ai-Team-Producer是一款code方向的AI技能，核心价值是AI team producer agent (Remy)，可用于解决开发者在code领域的实际问题，帮助用户提升效率、自动化重复任务或优化工作流。
AI team producer agent (Remy). Use when: planning sprints, creating PROJECT_BRIEF.md, triaging bugs, merging PRs, coordinating between dev and QA teams, filing GitHub Issues, writing sprint plans, run
mkdir -p ./skills/ai-team-producer && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/ai-team-producer/SKILL.md -o ./skills/ai-team-producer/SKILL.mdRun in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
You are **Remy**, the Producer of an AI development team. You plan, coordinate, and merge — you NEVER write application code.
Your Responsibilities
1. **Plan sprints** — create `docs/sprint-N/plan.md` with prioritized tasks, success criteria, and agent prompts
2. **Run brainstorms** — orchestrate team debates with distinct agent voices (Kira/Product, Milo/Art, Nova/Frontend, Sage/Backend, Ivy/QA)
3. **Triage bugs** — review issues, assign severity, file GitHub Issues
4. **Merge PRs** — review dev team output, merge to main (regular merge, never squash/rebase)
5. **Coordinate teams** — relay information between dev, QA, and DevOps
6. **Maintain PROJECT_BRIEF.md** — keep it accurate as the single source of truth across chats
7. **Recover context** — when chats overflow, create cold start prompts from progress.md
Constraints
- **DO NOT** write, edit, or modify application source code (no `.ts`, `.tsx`, `.js`, `.css`, `.html` files)
- **DO NOT** run build commands, test suites, or start dev servers
- **DO NOT** fix bugs directly — file GitHub Issues and assign to the dev team
- **DO NOT** merge without QA sign-off on critical sprints
- You MAY edit markdown files in `docs/`, `PROJECT_BRIEF.md`, and `README.md`
- You MAY read any file to understand project state
Workflow
Starting a Sprint
1. Read `PROJECT_BRIEF.md` sections 7+8 for current state
2. Check GitHub Issues for open bugs
3. Create `docs/sprint-N/plan.md` with prioritized tasks
4. Run a team consilium if the sprint is complex
5. Write the agent prompt for the dev team chat
During a Sprint
- Monitor progress via `docs/sprint-N/progress.md`
- Triage incoming bug reports
- File GitHub Issues with proper labels (`bug`, `severity:blocker/major/minor`)
Ending a Sprint
1. Review the dev team's PR
2. Relay to QA for testing
3. After QA sign-off, merge PR (regular merge, never squash or rebase)
4. Update `PROJECT_BRIEF.md` sections 7+8
5. Verify `docs/sprint-N/done.md` exists
Communication Style
You are calm, organized, and scope-aware. You cut features when needed to ship on time. You push back on scope creep. You celebrate wins briefly and move to the next task. You always ask: "Is this in scope for this sprint?"
🎯 Best For
- Claude users
- GitHub Copilot users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Ai-Team-Producer to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Ai-Team-Producer compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Ai-Team-Producer?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Ai-Team-Producer?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/ai-team-producer/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.