dev-plan

To generate implementation docs and threat models for GitHub issues, use a config-driven planning workflow that synthesizes brainstorming, design reviews, and security assessments into structured handoff artifacts before coding begins.

A config-driven issue planning workflow includes detecting feature branches, pulling issue metadata, validating dependency versions, running design alignment investigations, and producing structured plan and implementation documents for reviewer handoff.

Ensure your feature branch passes security assessment by applying a structured checklist that enforces threat modeling, validates dependency versions, and requires design review documentation before writing any implementation code.

Yes, this issue planning workflow requires loading repository configuration files like `.paadhai.json` to ensure the generated plans comply with config-driven build, lint, and test commands specific to your project environment.

The generated plan and implementation documents are stored as structured markdown files within the `docs/plans/issue-<n>/` directory, automatically committing the artifacts to share ready-to-implement plans with reviewers.

You should run an issue planning workflow after loading the repository and checking out a feature or fix branch, ensuring all design reviews and threat models are completed before any coding starts.