analyst

To turn vague requirements into a concrete task plan, you submit the proposed change to generate a formal proposal and a detailed .agent-task.md file. This process produces structured planning artifacts with SMART scope and acceptance criteria.

Generating a formal change proposal with Arc42 and C4 alignment involves analyzing proposed changes during the specification phase. This produces a machine-readable proposal.md that ensures traceability to architectural standards.

Yes, you can validate specifications using BDD standards through the final health assessment phase. The process ensures outputs map to BDD standards and reference relevant specs for traceability.

To start the discovery phase for an ambiguous change request, submit a clear requirement and request a Phase 1 plan. The tool outputs a proposal.md, a .agent-task.md, and guidance for validation.

From software specification and planning, you should expect a proposal.md, a .agent-task.md, and a final health assessment. These machine-readable outputs outline rationale, scope, and breaking changes.

Yes, this approach works without external dependencies for requirement analysis. The process operates independently to transform ambiguous change requests into structured documentation and validation artifacts.