Skip to content

Clarify custom checklist ownership and lifecycle - #4028

Open
WOLIKIMCHENG wants to merge 2 commits into
github:mainfrom
WOLIKIMCHENG:docs/3979-checklist-lifecycle
Open

Clarify custom checklist ownership and lifecycle#4028
WOLIKIMCHENG wants to merge 2 commits into
github:mainfrom
WOLIKIMCHENG:docs/3979-checklist-lifecycle

Conversation

@WOLIKIMCHENG

Copy link
Copy Markdown
Contributor

Summary

  • Clarify that custom /speckit.checklist outputs are reviewer-owned requirements-quality artifacts.
  • Define custom checklist [x] markers as requirements-quality approval, not implementation completion.
  • Update /speckit.implement guidance to treat checklist markers as a read-only gate and distinguish the built-in checklists/requirements.md lifecycle.

Closes #3979

Validation

  • git diff --check -- docs/quickstart.md docs/reference/agentic-sdd.md templates/commands/checklist.md templates/checklist-template.md templates/commands/implement.md
  • PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest -p no:cacheprovider tests/test_command_template_py_scripts.py -q

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Clarifies ownership and lifecycle semantics for custom versus built-in checklists.

Changes:

  • Defines custom checklists as reviewer-owned requirements-quality artifacts.
  • Makes implementation treat checklist markers as read-only gates.
  • Documents distinct built-in requirements.md behavior.
Show a summary per file
File Description
docs/quickstart.md Updates checklist and implementation guidance.
docs/reference/agentic-sdd.md Documents ownership and lifecycle distinctions.
templates/commands/checklist.md Adds reviewer ownership rules.
templates/checklist-template.md Defines checkbox semantics and lifecycle notes.
templates/commands/implement.md Makes checklist state read-only during implementation.

Review details

Tip

Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

  • Files reviewed: 5/5 changed files
  • Comments generated: 1
  • Review effort level: Balanced

Comment thread docs/quickstart.md Outdated
### Step 8: `/speckit.implement` — build it

Executes the tasks in `tasks.md` in dependency order. Run it once to build everything, or scope it to one phase at a time for large features.
Executes the tasks in `tasks.md` in dependency order. Before implementation, it reads checklist checkbox state as a gate and asks before proceeding if any checklist items are unchecked; it does not change custom checklist markers. Run it once to build everything, or scope it to one phase at a time for large features.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the quickstart implement step to state that implementation does not change any checklist files or markers, and called out that checklists/requirements.md is maintained by /speckit.specify and /speckit.clarify while custom checklists remain reviewer-owned.

@mnriem mnriem left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please address Copilot feedback

@WOLIKIMCHENG

Copy link
Copy Markdown
Contributor Author

Addressed the Copilot feedback by clarifying in the quickstart that implementation does not modify checklist files or markers, and by calling out that checklists/requirements.md is maintained by /speckit.specify and /speckit.clarify while custom checklists remain reviewer-owned.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review details

Suppressed comments (3)

templates/checklist-template.md:39

  • Use “requirements-quality” consistently with the ownership text above; “requirement-quality” here appears to be a typo.
- Mark items `[x]` only after review confirms the requirement-quality criterion is satisfied

templates/commands/checklist.md:148

  • Reserve requirements.md when choosing the custom checklist filename. The current domain-derived naming can select requirements.md, and the append behavior would then mix reviewer-owned items into the built-in checklist that specify/clarify automatically update (or allow specify to overwrite a custom file).
   - Leave every newly generated item unchecked (`[ ]`); checkbox state belongs to the reviewer

docs/quickstart.md:86

  • Use “requirements-quality” consistently; this sentence currently switches to the singular form immediately after introducing “requirements-quality review artifacts.”
Generates a custom quality checklist — "unit tests for your requirements" — to confirm the spec is complete, clear, and consistent before you break the work down. These custom checklists are reviewer-owned requirements-quality review artifacts: mark an item `[x]` only when the reviewer determines that requirement-quality criterion is satisfied. Checked custom items do not mean implementation work is complete.
  • Files reviewed: 5/5 changed files
  • Comments generated: 0 new
  • Review effort level: Balanced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Clarify custom checklist ownership and lifecycle

3 participants