task-analysis

Analyze a feature request against an existing codebase to frame implementation tasks by comparing the request with repository context, generating a structured task framing, and persisting it under tmp/tasks/<task-name>/task.md.

The best way to compare implementation paths is to generate one or more solution_N.md option files outlining different approaches, align evaluation criteria with humans when tradeoffs exist, and recommend a concrete path with explicit reasoning.

Ensure traceability of decisions when planning codebase changes by persisting task framing and solution options as markdown files, documenting rationale for tradeoffs, and recommending a concrete implementation path with explicit reasoning.

Yes, you can align evaluation criteria with team members before choosing a software solution by generating multiple solution_N.md option files and documenting the rationale for tradeoffs to reach a shared, concrete implementation recommendation.

Generate multiple solution options instead of directly implementing a task when tradeoffs exist between approaches, allowing you to align evaluation criteria with humans and document explicit reasoning before recommending a path.