inspequte-rule-plan

To draft a rule plan for a static analysis rule, you generate a `plan.md` file that defines the rule scope, detection strategy, implementation risks, and constraints. This ensures a structured approach to rule development without creating specification documents.

A static analysis rule plan is a foundational document outlining the problem, detection strategy, and potential risks for a new code quality rule. It structures the development process by defining scope and constraints before implementation begins.

Documenting implementation risks for code quality rules involves adding a checklist of potential risks to the rule plan. This checklist identifies edge cases and constraints associated with the rule's detection logic.

No, the rule planning process only affects the `plan.md` file and leaves `spec.md` untouched. It focuses strictly on defining rule scope and risks during the planning phase rather than generating specification documents.

Generating a static analysis rule plan requires context from existing rule documentation and agent guidelines. This context ensures the generated plan accurately reflects the target rule ID and the intended code quality checks.