analysis-phase

The analysis-phase skill serves as a critical quality gate within the Spec-Flow development lifecycle. It is designed for software engineers and architects who need to maintain strict traceability and architectural integrity between high-level requirements and low-level code implementation. By systematically checking the alignment of specification documents, implementation plans, and granular task lists, the agent ensures that no requirement is forgotten and no orphan task remains unmapped.

• Performs automated cross-artifact validation to ensure spec-to-plan and plan-to-task coverage.

• Detects potential breaking changes across API signatures, database schemas, UI component interfaces, and authentication flows.

• Validates dependency trees, ensuring all imports, integrations, and external modules are documented and accounted for.

• Generates a structured analysis-report.md file containing actionable findings, impact assessments (High/Medium/Low), and recommended remediation steps.

• Updates state.yaml to reflect progression, enabling seamless integration with CI/CD pipelines.

• Supports TDD-focused workflows by ensuring task acceptance criteria explicitly map to feature success criteria.

• Inputs: Requires spec.md, plan.md, and tasks.md as core artifacts for the current feature or epic.

• Usage: Invoke during the /analyze phase of the Spec-Flow workflow to prevent post-deployment integration failures.

• Constraints: Strictly enforces the mapping of all spec requirements to corresponding implementation tasks. Missing mappings or unvalidated dependencies are flagged as failures.

• Best Practice: Use this skill prior to the implementation and optimization phases to catch design flaws early when they are least expensive to resolve. Explicitly scan for pattern-based breaking changes rather than assuming alignment.