dev-team

Topics in the source

• Dev Team
• When to Activate
• When NOT to Use
• Personas
• Workflow
• 1. Extract the topic
• 2. Build a bounded project-context summary
• 3. Launch four personas in parallel

Run a multi-persona session where PM, Architect, Developer, and QA each respond from their own perspective in a single turn. This is the preset four-lens review for collaborative design and planning. It is not adversarial challenge (council), and it is not a free-form team composer (team-builder selects arbitrary agents; dev-team always runs the same four roles). The user provides a topic — a feature description, proposal, story, or question. The skill runs all four personas in parallel as independent subagents, then presents their responses together. Use when: Designing a new feature and wanting PM, Architect, Dev, and QA concerns surfaced at once Reviewing a proposal before committing to implementation Onboarding an initiative and wanting each role to define their first concerns User says "what would the team think about this", "give me all perspectives", or "run this by the team" Starting a story and wanting role-specific input before writing a single line of code | Condition | Use Instead | | --- | --- | | Ambiguous go/no-go decision with real tradeoffs | council | | You want to hand-pick which agents participate | team-builder | | Single-role deep-dive (e.g. architecture only)

This is an excerpt. Refer to the complete source and its current requirements.