roadmap: portable AI-native SDLC - #148
Conversation
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f70aeac5a9
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - **Risk sets the plan gate.** High-risk work — constitution paths, workflows, | ||
| identity/auth, security controls, migrations, deployment/production infrastructure, | ||
| or broad architecture — requires the operator to accept `plan.md` before code. | ||
| Routine work may keep plan + code in one PR only after an independent plan check | ||
| records acceptance before the write phase. The author cannot accept its own plan. |
There was a problem hiding this comment.
The current in-session path still tells yshifu to spawn a coder immediately after an issue gets ready (manager/CLAUDE.md:395-397 and templates/yshifu-command.md:23), with no risk check or accepted-plan step. As a result, the next high-risk issue can start implementation after only spec approval or manager consensus, even though this change makes operator acceptance of the exact plan a current safety rule. Update the live manager/template instructions or keep this rule explicitly future-only until that path enforces it.
AGENTS.md reference: AGENTS.md:L54-L58
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 4cd48b4. The risk-tier plan gate is now explicitly accepted target policy, not current behavior. AGENTS.md, README.md, and work/README.md all say the current manager does not enforce it yet, and this directions-only PR does not claim or wire a live gate.
| the **constitution paths** — `.github/**`, `.claude/**`, `AGENTS.md` (this file), | ||
| `CLAUDE.md`, `REVIEW.md` — such changes land as patches under `proposals/` that the | ||
| `CLAUDE.md`, `REVIEW.md`, `ROADMAP.md` — such changes land as patches under `proposals/` that the | ||
| operator applies. That is the same list `REVIEW.md` uses; the two must always match, so |
There was a problem hiding this comment.
This adds ROADMAP.md to the constitution paths, but proposals/README.md:3-4 still defines that set without it. That leaves the guide for constitution patches out of sync with the new rule and can cause future work to omit the required proposal treatment for roadmap changes. Update that list alongside the two lists changed here.
AGENTS.md reference: AGENTS.md:L94-L100
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 4cd48b4. proposals/README.md now includes ROADMAP.md, so its constitution-path list matches AGENTS.md and REVIEW.md.
Deploying ystack with
|
| Latest commit: |
4cd48b4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7cef934d.fabrica-6yx.pages.dev |
| Branch Preview URL: | https://codex-playbook-roadmap.fabrica-6yx.pages.dev |
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
1 participant
What changes
Scope
This PR changes direction and policy documents only. It does not add or enable an autonomous workflow. It does not change the live /yshifu installation. The first implementation intent is deliberately kept out of this PR and will use the normal G1 artifact gate after this direction is accepted.
Review fixes
Verification
Verified on 4cd48b4:
Closes #147