docs(readme): clarify the feature delivery flow - #717
Open
alexsoyes wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
:) |
alexsoyes
enabled auto-merge (squash)
August 25, 2026 07:56
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.
🎯 What & why
Clarifies the README Golden Path so a feature starts from a functional need or User Story, becomes a tracked issue or ticket, and continues through production and durable learning.
🛠️ How it works
Replaces the single-row feature loop with three readable stages: Frame, Deliver, and Ship. Removes the standalone commit step because implementation already owns phase commits, and makes project-specific shipping explicit.
🧪 How to verify
node scripts/sync-readme-counts.mjs --check.node scripts/check-markdown-links.js.✅ I certify