Coordinate spec-driven team implementation from discovery to merge.
npx skills add https://github.com/darkquasar/patronus --skill team-implement-darkquasar
Please help me install this Agent Skill. Skill: team-implement Source: https://github.com/darkquasar/patronus/tree/main/claude/skills/team-implement Command: npx skills add https://github.com/darkquasar/patronus --skill team-implement-darkquasar
This Skill orchestrates a spec-driven team implementation workflow, turning research specs into a managed collaboration that spawns dedicated teammates and coordinates their work, reducing manual project setup overhead.
Provide your research domain path and let the Team Lead set up the cooperative workflow.
High-intent search queries and answers about installing and using this skill.
To coordinate parallel feature implementation from a spec, this Skill derives clear boundaries from your tasks.md and assigns them to up to five teammates. It ensures separable file ownership and guides Phase 0 through Phase 6 from discovery to merge.
Spec-driven team workflow automation creates isolated git worktrees for each spawned teammate to ensure parallel work does not conflict. It tracks progress via TaskList and enforces an approved tasks.md to maintain structured development boundaries.
Yes, you need a research domain path containing your feature spec and an approved plan.md to start spec-driven team implementation. The Team Lead uses these inputs to scope the work, assign tasks, and enforce separable file ownership across teammates.
The maximum number of teammates supported for coordinated project management is five. The Skill spawns these teammates to execute feature work across multi-domain research domains, creating isolated worktrees for each to ensure parallel implementation without file conflicts.
When a spec-driven team implementation finishes, it generates a provenance index documenting the completed feature work. This index is written upon completion of Phase 6, providing a tracked record of the cooperative workflow from initial discovery to merge.
No, you cannot use spec-driven team coordination without an approved tasks.md file. The workflow explicitly enforces the tasks.md to derive clear boundaries, assign work to teammates, and guide the phase-driven execution from discovery through provenance.
itsHabibExecute approved plans by spawning parallel teammate tasks for deliverable creation.
cuiossCommit, push, and manage pull requests to finalize a plan.
imgompandaCoordinate multi-agent teams on a shared task board.
CaptainCrouton89Coordinate multiple Claude Code sessions to manage agent teams.
