Anyone combining task management with Spec-driven development in MCP?

[Pangu-Immortal]

Hi everyone,

I've been thinking about how task management MCP tools could integrate with Spec-driven development workflows.

The idea is: instead of just tracking tasks, also manage the specifications (architecture docs, API contracts, data models) that drive those tasks — with change proposals, conflict detection, and verification.

I've been experimenting with this approach in a project called qflow, which combines both in a single MCP server:

• Task management (dependency DAG, 7-state machine, complexity scoring)
• Spec lifecycle (propose → apply → verify → archive, with SHA-256 conflict detection)
• Multi-persona review (12 agent roles for adversarial code review)
• Context modules (load platform-specific design rules on demand)

Curious if anyone else has explored similar integrations, or if you think task management and spec management are better kept separate?

Would love to hear your thoughts.