Improving Spec Kit: Adding Specialized Sub-Agents to /implement

[4mb1t10n]

The Current Strength: Spec Kit excels at methodical PRD planning and project structuring. The planning phase is solid.

The Gap: The /implement command currently operates as a single agent trying to handle all implementation tasks. This creates inefficiencies, especially for specialized work.

The Comparison: I've been using Taskmaster for a few months, and while it struggles with PRD planning (where Spec Kit shines), its implementation approach using specialized sub-agents is fantastic.

The Proposal: Transform /implement into an orchestrator that delegates to specialist sub-agents.
Here's how it would work:

• /implement becomes an orchestrator agent that analyzes each task
• It routes work to the appropriate specialist (database engineer, frontend dev, API designer, etc.)
• Each specialist maintains its own context and best practices

The Key Benefit: We eliminate context pollution. Right now, we have to load database design patterns into the main agent's context even when it's working on frontend tasks. With specialists, database knowledge lives with the database agent, frontend patterns with the frontend agent, and so on.

Bottom Line: Combine Spec Kit's planning strength with Taskmaster's implementation approach. Best of both worlds.

[harikrishnan83]

@4mb1t10n Here is a writeup on how I got Spec Kit to use Claude Sub Agents - https://www.linkedin.com/pulse/spec-driven-development-beyond-first-feature-api-design-krishnan--lbyec. This also helps with parallel execution.

Is this on the lines of what you had in mind?

[4mb1t10n]

Awesome thank you!

[marcelomarkus]

Has anyone managed to do this with the co-pilot?