Conversation
…rate workflow Real-world encounter (llm-wiki, 2026-05-02) surfaced that the planned "explicit choice (init-project vs ad-hoc)" exit criterion is too thin -- plain init-project on a project with existing docs/design-decisions.md, docs/concept.md, docs/PROCESS.md, docs/plans/, and claude-memory artifacts would scaffold empty stubs that duplicate or contradict reality. Adds a Scope Clarification subsection to M010 with a concrete 5-step detect-analyze-migrate flow (detect candidate artifacts -> analyze mapping + conflicts + gaps -> migrate per-artifact with user approval -> scaffold gaps only -> update entry-point docs) and 3 open design questions for plan-milestone to resolve. Suggests this likely warrants a new ytstack:adopt-brownfield skill triggered by using-ytstack when no-.ytstack/ + repo has candidate artifacts. Adds matching exit criterion: brownfield-without-.ytstack init MUST run a detect-analyze-migrate pass, not scaffold from empty templates.
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
Why
llm-wiki has `docs/design-decisions.md`, `docs/concept.md`, `docs/PROCESS.md`, `docs/plans/`, and claude-memory `project_*.md` -- it's neither greenfield-empty nor a repo with an existing `.ytstack/`. Plain `init-project` would scaffold empty stubs that duplicate or contradict the existing artifacts. Greenfield flow (office-hours -> plan-ceo-review -> init-project) is also wrong because the project is validated by months of artifacts, not awaiting validation.
What's added
Documentation only. No code changes.
Test plan
Note
Low Risk
Documentation-only change that refines milestone scope/exit criteria; no runtime behavior or tooling is modified.
Overview
Updates
.ytstack/ROADMAP.mdto tighten M010’s exit criteria: brownfield repos without.ytstack/must go through a detect → analyze → migrate adoption pass (with per-artifact user choices) before scaffolding any missing files.Adds a detailed scope clarification including candidate artifact mappings, the follow-on steps (scaffold gaps and update entry-point docs), and open design questions (e.g., whether to generate an
ADOPTION-PLAN.md, how to handle ADR archives, and how this interacts withoffice-hours).Reviewed by Cursor Bugbot for commit 1c24817. Bugbot is set up for automated code reviews on this repo. Configure here.