Skip to content

sprint-plan: revise Phase 2 wording to acknowledge feasibility-gate skip in lean/solo #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
specterslient95-lgtm wants to merge 1 commit into
base: main
Choose a base branch
from
Open

sprint-plan: revise Phase 2 wording to acknowledge feasibility-gate skip in lean/solo #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude/skills/sprint-plan/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ See `.claude/docs/director-gates.md` for the full check pattern.

For `new`:

**Generate a sprint plan** following this format and present it to the user. Do NOT ask to write yet — the producer feasibility gate (Phase 4) runs first and may require revisions before the file is written.
**Generate a sprint plan** following this format and present it to the user. Do NOT ask to write yet. If the resolved review mode is `full`, the producer feasibility gate (Phase 4) runs first and may require revisions before the file is written. If the mode is `lean` or `solo`, Phase 4 is skipped (see Phase 4) and the QA plan gate (Phase 5) becomes the next checkpoint — the user takes on the feasibility-review responsibility themselves at the write-approval step.

```markdown
# Sprint [N] — [Start Date] to [End Date]
Expand Down