feat: add /feature-scope skill — guided scoping before implementation#415
Open
jnMetaCode wants to merge 1 commit intogarrytan:mainfrom
Open
feat: add /feature-scope skill — guided scoping before implementation#415jnMetaCode wants to merge 1 commit intogarrytan:mainfrom
jnMetaCode wants to merge 1 commit intogarrytan:mainfrom
Conversation
Bridges the gap between /office-hours (idea validation) and /plan-eng-review (architecture). Five phases: 1. Context gathering — reads design docs, TODOS, codebase 2. Goal clarification — 5 forcing questions (who, done, simplest, deferred, touchpoints) 3. Scope definition — acceptance criteria, deferred items, risks 4. Implementation slices — ordered, independently shippable PRs 5. Save & handoff — persists to ~/.gstack/projects/$SLUG/ Hard gate: produces a scoping doc, not code. Closes garrytan#318
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
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
Adds
/feature-scope— a new skill that bridges the gap between/office-hours(idea validation) and/plan-eng-review(architecture lockdown). This is the missing step identified in #318.Lifecycle position:
What it does
Five phases:
~/.gstack/projects/$SLUG/Hard gate: Produces a scoping doc, not code. Same pattern as
/office-hours.The 5 forcing questions
Operating principles
Files
feature-scope/SKILL.md.tmpl{{PREAMBLE}},{{SLUG_EVAL}})feature-scope/SKILL.mdbun run gen:skill-docsafter merge to inject standard preamble)Test plan
/feature-scopeproduces a scoping doc with all 6 sections/office-hoursdesign docs when available~/.gstack/projects/$SLUG/feature-scope-*.md/plan-eng-reviewor/plan-ceo-reviewas next stepsCloses #318