analyze-task

To analyze a complex repository task, generate a structured Analysis Brief to clarify goals, define boundaries, and document data/type/interface decisions before coding. This structure-first approach ensures explicit scope and reduces rework by securing alignment upfront.

Task analysis for software architecture and large rewrites is needed when work is non-trivial and involves multiple layers. It produces an Analysis Brief covering contract impacts, test strategy, and subagent justification to prevent ambiguity and misalignment across teams.

Defining product boundaries and non-goals requires a structured analysis phase that explicitly documents scope limitations. By generating an Analysis Brief, you outline canonical-doc impacts and layer changes, ensuring the feature implementation stays within approved boundaries.

The best way to justify using a subagent for architecture tasks is to evaluate the task complexity within an Analysis Brief. This brief explicitly determines whether subagent use is justified for high-effort work, providing a clear path for alignment and handoff.

Yes, you can use task analysis to prepare for cross-team architectural alignment. The process generates an Alignment-ready state by documenting risks, ambiguities, and specific alignment questions, serving as a foundation for discussion before implementation.