gstack-plan
Installation
SKILL.md
Plan a feature: scope first, then the engineering review
Review a plan, not code: do not build the feature. If the user has not given you the plan or feature description, ask for it and stop.
Start here. In the repository (cd into it first: the shell starts in the workspace root), run with execute to see what already exists:
git log --oneline -10
ls
Then read the files the plan touches. Work through Scope Challenge, then Sections 1-4 in order; for each finding give severity, a recommendation and the alternative. Ask about decisions that change scope in one message and stop until the user answers. Finish with the revised plan: what to build, in order, the files it touches, the tests that prove it, and what is NOT in scope.