workflow-analyze

To generate an Architecture Decision Record, input your issue description to parse the problem, investigate 2-4 solution approaches with pros and cons, and output a structured ADR assessment document with decision confidence.

Analyzing and comparing technical solutions involves defining the problem scope, evaluating multiple architectural approaches against coding principles, and documenting objective criteria to guide decisive or advisory recommendations.

Documenting decision-making processes requires structuring problem definitions, solution investigations, final selections, and completion criteria into a standardized analysis document to ensure balanced analysis and honest assessment.

Yes, this analysis approach strictly adheres to Korean-language documentation, generating the analysis.md file in the docs/work/{task-name}/ directory while maintaining neutral language and anti-bias rules throughout.

A problem definition should outline the current situation, the problem to solve, and desired goals with concrete examples, ensuring the scope and confirmation needs are clearly established before investigating solutions.

Limitations include strict adherence to documentation writing order, balanced analysis principles, and anti-bias rules, requiring honest decision assessment and neutral language which may constrain rapid, informal brainstorming sessions.