plan-deep-review

A deep architecture review assesses software development plans by evaluating architecture, security, performance, and deployment readiness. It detects review context from Git or plan documents, challenges premises, and maps failure modes to ensure robust alignment with strategic goals.

Identifying failure modes and concurrency risks requires mapping architectural concerns during a plan review. This process evaluates API contracts, detects potential structural flaws, and generates an error registry to highlight deployment vulnerabilities before development proceeds.

Risk assessment works by automatically detecting the review context, whether it is a Git pull request, a standalone plan document, or a hybrid combination. It then challenges premises and evaluates API contracts to map potential failure modes specific to that input source.

Yes, you need Python, Git, and various command-line tools like grep and glob to perform this automated plan review. These dependencies are required for code analysis, context detection, and generating structured documentation like error registries and diagrams.

A go/no-go readiness verdict is a structured output that determines whether a software development plan is secure and robust enough to proceed. It results from evaluating deployment plans, assessing API contracts, and mapping potential failure modes.

Use scope reduction to narrow a plan's focus or selective expansion to target specific areas during a deep plan review. These modes, along with hold scope and scope expansion, adjust the review's depth to match your project's current risk assessment and strategic needs.