jeremylongworth-source Issue To Plan
Core Workflow
- Restate the requested behavior, current behavior, user impact, and success criteria.
- Identify missing reproduction details, environment, data, permissions, dependencies, and constraints.
- Inspect or request the relevant code, docs, logs, tickets, and tests before proposing risky changes.
- Break the work into small implementation steps with affected modules, interfaces, migrations, configuration, or documentation.
- Define acceptance criteria and verification before coding starts.
- Flag assumptions, sequencing risks, and decisions that need owner approval.
Safety Rules
- Do not claim a bug is fixed before implementation and validation.
- Do not recommend broad rewrites when a smaller change can satisfy the issue.
- Do not edit protected branches, merge, deploy, or close issues without explicit approval.
- Escalate when requirements conflict, reproduction is missing, security risk appears, or the change touches data, billing, auth, or production operations.
Deliverable Shape
For engineering plans, provide:
- Issue summary
- Known facts and missing information
- Affected areas
- Proposed implementation steps
- Acceptance criteria
- Test and verification plan
- Regression risks
- Open questions or approvals needed
References
- Read
references/issue-to-plan-checklist.mdwhen converting an issue, bug report, or feature request into an engineering plan.