backlog-technical-project-manager

The backlog-technical-project-manager is a specialized skill designed to orchestrate complex development workflows within Backlog.md environments. It acts as a high-level coordinator that delegates granular implementation tasks to sub-agents, ensuring that codebase changes remain modular, dependency-safe, and aligned with project-wide acceptance criteria. This skill is intended for software engineers and technical leads who use Backlog.md to manage tasks, codebases, and architectural decisions, providing a systematic approach to AI-assisted software delivery through the spec-driven development methodology.

• Orchestrates complex task delivery by breaking down project goals into isolated implementation tasks for specialized sub-agents.

• Enforces strict quality gates, including reviewing and approving implementation plans before coding begins to prevent scope creep or redundant work.

• Manages dependencies and overlapping code regions by creating serial execution lanes for conflicting tasks while allowing parallel workflows for independent units.

• Validates business outcomes and Definition of Done (DoD) requirements, ensuring that each task is not marked as complete without verifiable evidence, such as end-to-end user flow logs or passing test suites.

• Maintains project consistency by ensuring that sub-agents correctly update git branches, task records, and documentation within the Backlog.md project structure.

• Activate this skill explicitly when you need to delegate coordination, such as saying 'Act as TPM' or 'Coordinate these tasks'.

• Operates by managing dedicated git clones for each task to ensure workspace isolation, preventing cross-agent file interference.

• Acts as the primary validator for sub-agent output; it does not perform deep coding itself but ensures that implementation, research, and blast-radius analysis are performed correctly by delegated agents.

• Requires adherence to Backlog.md workflow resources, including task-creation, execution, and finalization protocols.

• Focuses on maintaining operational memory by documenting common agent failure patterns and suggesting improvements to DoD checklists based on recurring issues.

• TPM is authorized to troubleshoot environments and install necessary dependencies to unblock verification pipelines, ensuring that the development loop remains uninterrupted.