docs: add hands-off orchestration example#2801
Conversation
Signed-off-by: meow2149 <maojiuyuqi794@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Pull request overview
Adds a new community documentation page demonstrating an artifact-first “hands-off orchestration” flow (specify → clarify → plan → checklist → tasks → analyze) with explicit stop conditions before issue creation or implementation, and links it into the docs navigation.
Changes:
- Add a new “Hands-Off Orchestration” community doc page with guardrails and copy/paste prompts.
- Link the new page from the Community TOC and the Community Walkthroughs index.
Show a summary per file
| File | Description |
|---|---|
| docs/toc.yml | Adds a new Community nav entry for the hands-off orchestration page. |
| docs/community/walkthroughs.md | Adds a bullet linking to the new hands-off orchestration doc from the walkthroughs index. |
| docs/community/hands-off-orchestration.md | Introduces a new documentation example describing the hands-off orchestration pattern and prompts. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 3/3 changed files
- Comments generated: 4
Signed-off-by: meow2149 <maojiuyuqi794@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
| 1. Run /speckit.specify for the requested feature. | ||
| 2. Run /speckit.clarify to identify ambiguity. If a real product decision is required, stop and ask me before continuing. | ||
| 3. Run /speckit.plan after the specification is clear enough to plan. | ||
| 4. Run /speckit.checklist and fix requirement-quality gaps by looping back to /speckit.clarify or /speckit.specify as needed. | ||
| 5. Run /speckit.tasks after the plan and checklist are consistent. | ||
| 6. Run /speckit.analyze to check cross-artifact consistency. |
There was a problem hiding this comment.
Addressed in 5154d17 by swapping the numbered prompt steps so /speckit.checklist runs before /speckit.plan, with wording updated to plan only after the requirements checklist passes.
| - Generate and review artifacts before creating issues or writing code. | ||
| - Ask the user when a product decision is required. | ||
| - Loop back to an earlier stage when a later stage finds stale, incomplete, or inconsistent artifacts. | ||
| - Do not run `/speckit.taskstoissues` unless the user explicitly requests issue creation. | ||
| - Do not run `/speckit.implement` unless the user explicitly requests implementation. |
There was a problem hiding this comment.
Addressed in 5154d17 by adding a visible note and guardrail that this conservative example uses only README.md and DESIGN.md as in-repo guidance sources unless the user explicitly provides more context.
|
|
||
| These examples are maintained in the Spec Kit documentation: | ||
|
|
||
| - **[Hands-off orchestration example](hands-off-orchestration.md)** — Shows an artifact-first flow that runs specify, clarify, plan, checklist, tasks, and analyze, then stops before issue creation or implementation unless the user explicitly opts in. |
There was a problem hiding this comment.
Addressed in 5154d17 by updating the walkthrough summary to list checklist before plan, keeping it consistent with the recommended workflow.
Co-authored-by: Cursor <cursoragent@cursor.com>
Description
Adds a website documentation example for an artifact-first hands-off orchestration pattern. The example follows the maintainer direction in #2789 to start with a docs example, and shows how to run specify, clarify, plan, checklist, tasks, and analyze before stopping unless the user explicitly opts into issue creation or implementation.
Fixes #2789
Testing
uv run specify --helpuv sync && uv run pytestAdditional validation:
git diff --checknpx -y markdownlint-cli2 "docs/community/hands-off-orchestration.md" "docs/community/walkthroughs.md"AI Disclosure
This PR was prepared with Cursor AI assistance. I reviewed the issue discussion, scoped the change to documentation, ran local validation, and created this draft PR for maintainer feedback.
Made with Cursor