analyze-task

Produce a structured Analysis Brief for non-trivial repository tasks.

192|7|Updated Dec 30, 2025

Search Tags:#planning #architecture #subagent #alignment #analyze #task-analysis

Ready to run

npx skills add https://github.com/yusifeng/formax --skill analyze-task-yusifeng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-task
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/analyze-task
Command: npx skills add https://github.com/yusifeng/formax --skill analyze-task-yusifeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies goals, boundaries, and decisions for non-trivial repository work before coding or writing todos, reducing misalignment and rework.

Core Features & Use Cases

Produce a structured Analysis Brief documenting Goal, Product Boundary, Scope, Non-goals, Canonical-Doc Impact, Data / Type / Interface First, Layer Impact, Risks / Ambiguities, Need Subagent?, Test Strategy, Alignment Questions, and Ready for Todo?.
Outline whether a subagent is justified (xhigh or local) and provide a path to alignment and handoff to write-task-todo.
Serve as a foundation for cross-team discussions and architectural decisions before implementation.

Quick Start

Run analyze-task to generate an Analysis Brief for alignment on a complex repository task.

Frequently Asked Questions about analyze-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I analyze a complex repository task before writing code?▼

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.

When do I need task analysis for software architecture and large rewrites?▼

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.

How do I define product boundaries and non-goals for a feature implementation?▼

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.

What is the best way to justify using a subagent for architecture tasks?▼

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.

Can I use task analysis to prepare for cross-team architectural alignment?▼

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.