feat(workflow): 5-step default + Stop hook + planning-docs drift gate#23
Merged
shiniguchi merged 1 commit intomainfrom Apr 30, 2026
Merged
feat(workflow): 5-step default + Stop hook + planning-docs drift gate#23shiniguchi merged 1 commit intomainfrom
shiniguchi merged 1 commit intomainfrom
Conversation
…+ drift gate Retire the 19-row sequence (adapted from AiLine's old 21-row workflow, same root cause: never adopted in practice — 14 phases shipped without following the documented chronology). Replace with 5-step default that matches actual practice + add the planning-docs drift gate with three enforcement layers. Tailored for this project: - GSD as default planner, Superpowers as opt-in for KPI-math / typed SQL / refactor phases - GStack opt-in via Reach-for table only - Cloudflare Pages deploy mapping (CF Pages of main = DEV; branch deploys not enabled by default) - Reach-for table includes RLS + cohort/LTV math signals - Stop hook entry added alongside existing localhost-qa-gate Files: - docs/workflow.md: full rewrite (19-row → 5-step + Reach-for + drift gate) - .claude/hooks/next-step-hint.js: ported from AiLine — silent on non-feature/phase-* branches, detects step from .planning/phases/ - .claude/reach-for.json: NEW, includes ramen-specific signals (RLS, cohort/LTV math, Cloudflare/SvelteKit/Supabase docs) - .claude/scripts/validate-planning-docs.sh: ported from AiLine - .github/workflows/validate-planning.yml: NEW CI gate, blocks PR merge on drift for PRs touching SUMMARY/ROADMAP/STATE - .claude/settings.local.json: Stop hook entry for next-step-hint alongside existing localhost-qa-gate - .claude/CLAUDE.md: workflow section rewritten to point to new 5-step + planning-docs gate checklist - .planning/STATE.md: small drift backfill — total_plans 60→64, completed_plans 60→61, matching disk Smoke-tested: validator: ✅ planning docs in sync (after backfill) hook (on docs/workflow-v2): silent (correct — not a phase branch)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Port the workflow v2 pattern that shipped to AiLine (ailine-ai/shared-docs#62) — tailored for this repo's stack (SvelteKit + Cloudflare Pages + Supabase, solo-dev, single-repo).
Why
The 19-row workflow this repo had was adapted from AiLine's old 21-row sequence. Same root cause as AiLine: never adopted in practice. 14 phases shipped without following the documented chronology. Truth-in-documentation: replace with 5-step default that matches actual shipping pattern.
What changes
5-step default sequence (replaces 19 rows):
discuss → plan → execute → epic-end QA → ship.
Stop hook + Reach-for table (next-step-hint.js + reach-for.json):
On
feature/phase-*branches, prints→ Next: <command>after every turn. Detects current step from.planning/phases/<NN>-<slug>/artifacts. Reach-for table tailored for this project's signals (RLS, cohort/LTV math, Cloudflare/SvelteKit/Supabase docs).Planning-docs drift gate — three layers:
.claude/scripts/validate-planning-docs.shcompares ROADMAP[x]count, STATE.md frontmatter, and*-SUMMARY.mdon disk⚠️ Planning docs driftwarnings inline.github/workflows/validate-planning.ymlblocks PR merge when drift exists on PRs touching SUMMARY/ROADMAP/STATESmall drift backfill — STATE.md
total_plans60→64,completed_plans60→61 (matches disk).Tailored for this repo (vs AiLine version)
git push → CF Pages auto-deploy on main(notgh workflow run deploy_dev.yml)localhost-qa-gate.jsTest plan
docs/workflow-v2(correct — not a phase branch)