plan-to-github-issues

Plan to GitHub Issues

1. Locate the plan

Find **/plans/plan-*.md or ask. Repo: gh repo view --json nameWithOwner. Each ## Phase N: Title + - [ ] criteria.

2. Create labels

gh label create "phase" --color "#0052CC" --description "Implementation phase" --repo OWNER/REPO
gh label create "acceptance-criteria" --color "#5319E7" --description "Has acceptance criteria" --repo OWNER/REPO

3. Create one issue per phase

Title: Phase N: <Title>, labels phase/enhancement/acceptance-criteria, run in parallel.

Overview

<"What to build" content from the plan phase> Related user stories:

Acceptance Criteria

Test Coverage Requirements

Every checkbox needs a validating test; PR is blocked unless CI passes.

4. Create the CI workflow

Create .github/workflows/ci.yml via the Contents API:

On PR (open/sync/reopen) + push to main
Real Postgres+Redis containers, no mocks
deps → typecheck → migrate → test w/ coverage → upload artifact
acceptance-criteria-check job (PR-only): counts - [ ] via Closes #N, warns only
Lint job; adapt commands per package.json/bunfig.toml

gh api --method PUT /repos/OWNER/REPO/contents/.github/workflows/ci.yml \
  -f message="chore: add CI workflow with acceptance criteria tracking" \
  -f content="<base64>"

5. Create the PR template

Create .github/PULL_REQUEST_TEMPLATE.md (same API): Closes #N field, criteria checklist, criterion→test table, merge checklist.

6. Report back

List issue URLs, confirm paths. PRs add Closes #N; check criteria as proven; CI warns on unchecked.

Notes

Create issues in parallel. No checkout → Contents API for files. No overview → use title + criteria. Fake secrets only.