lead

Backlog decomposition breaks large items into iterative work units with clear acceptance criteria. This skill automates that process by structuring work streams and coordinating cross-functional subagents for dev, test, security, and documentation tasks.

Subagent coordination tracks responsibilities across dev, test, security, and doc-writer roles. The orchestration mechanism uses standardized prompts and structured iteration files to ensure clear handoffs and preserve context for new sessions.

Structured iteration files serve as the single source of truth for context and governance. They log decisions and maintain context transfer, allowing new sessions to resume planning without losing prior work history.

Planning cross-team backlog work requires decomposing items into repeatable iterations with standardized prompts. This approach ensures cross-team coordination, iteration planning, and decision logging are maintained via structured iteration files.

No specific dependencies are required to orchestrate backlog work end-to-end. The skill operates independently to decompose items, coordinate subagents, and maintain governance through iteration files and standardized prompts.

Automated iteration planning is less suitable for small, single-step tasks that do not require cross-functional subagent coordination. It is designed for complex items needing repeatable iterations across dev, test, security, and documentation workflows.