speckit-security-review-plan

To review planning artifacts for security weaknesses, examine Spec-Kit documents like plan.md, spec.md, and data-model.md to identify trust boundaries, authorization gaps, and unsafe assumptions before writing code.

A secure-by-design assessment for architecture planning evaluates authentication, data flow, validation, and deployment hardening across planning documents to flag vulnerabilities and ambiguous decisions early in the development lifecycle.

To catch missing security requirements in a feature spec or data model, run a security review on plan artifacts to generate a report detailing vulnerabilities, confirmed secure patterns, and missing deployment hardening.

Yes, you can apply threat modeling to Spec-Kit contracts and quickstart documents to evaluate trust boundaries, secrets handling, and logging mechanisms to ensure secure design principles are met before implementation.

The best way to check trust boundaries and data flow in planning documents is to review the complete plan package against secure design criteria, isolating vulnerabilities and unsafe dependencies before development starts.