AI Coding Spec Packet Generator

Turn a vague implementation request into four reviewable Markdown files before you ask an AI coding tool to touch the repo.

spec.mdScope, non-goals, constraints, risks

tasks.mdReviewable implementation slices

evidence.mdTests, screenshots, logs, stop signals

1. Describe the change

Requirement or feature name

Plain-language request

Write the messy version first. The output will make the review structure explicit.

Users or reviewers affected

2. Add boundaries for AI coding

Stack or repo context

Constraints

Non-goals

Known risks

Release signals to watch

From vague request to reviewable packet

Weak input

Improve notification settings.
Make it less confusing and support mobile push.

Spec-ready output

Goal:
- Make email, in-app, and push preferences explicit.

Non-goals:
- no new provider
- no pricing changes

Evidence:
- migration dry run
- duplicate notification test
- old mobile client screenshot

Where to use the packet

Before prompting AI

Paste the packet above the coding prompt and tell the assistant to implement only the listed scope.

Read the workflow

Inside a pull request

Attach acceptance criteria and evidence so reviewers can compare the diff against the original contract.

Open review checklist

As a repo template

Keep the generated files in /docs/specs/ or next to the issue that owns the change.

Open SDD template