docs: expand commands list and fix grep pattern in local-dev guide#2254
docs: expand commands list and fix grep pattern in local-dev guide#2254HumaizaNaz wants to merge 10 commits intogithub:mainfrom
Conversation
Update section title from 'Process' to 'Workflow'
Added new commands for specification clarification and task implementation.
Update installation instructions with new commands
Update command to check for executable shell scripts.
Fix grep pattern for shell script check
|
I apologize for the multiple commits. |
There was a problem hiding this comment.
Pull request overview
This PR updates documentation around local development and installation verification, including a small shell command correction and an expanded list of available /speckit.* slash commands after initialization.
Changes:
- Fixes the POSIX script filtering example in the local development guide by properly escaping the
.in the.shmatch. - Updates the post-init “available commands” list in the installation guide to include
/speckit.clarifyand/speckit.implementand normalize list formatting.
Show a summary per file
| File | Description |
|---|---|
| docs/local-development.md | Escapes the grep pattern for .sh when checking generated scripts. |
| docs/installation.md | Expands/rewrites the post-init command list shown to users. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
|
Please address Copilot feedback |
HumaizaNaz
changed the title
|
Both Copilot suggestions have been addressed — updated the commands list wording and PR title. Thank you! |
There was a problem hiding this comment.
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
| This helps verify you are running the official Spec Kit build from GitHub, not an unrelated package with the same name. | ||
|
|
||
| After initialization, you should see the following commands available in your coding agent: | ||
| After initialization, you should see some of the available commands in your AI agent: |
There was a problem hiding this comment.
This sentence switches terminology from the rest of the document (“coding agent” / “AI coding agent”) to “AI agent”. For consistency (and to avoid confusion with non-coding AI tools), consider using “AI coding agent” here as well.
| After initialization, you should see some of the available commands in your AI agent: | |
| After initialization, you should see some of the available commands in your AI coding agent: |
| After initialization, you should see some of the available commands in your AI agent: | ||
|
|
||
| - `/speckit.specify` - Create specifications | ||
| - `/speckit.plan` - Generate implementation plans | ||
| - `/speckit.tasks` - Break down into actionable tasks | ||
| - `/speckit.specify` - Create specifications | ||
| - `/speckit.clarify` - Clarify and refine specifications | ||
| - `/speckit.plan` - Generate implementation plans | ||
| - `/speckit.tasks` - Break down into actionable tasks | ||
| - `/speckit.implement` - Execute tasks and build the feature |
There was a problem hiding this comment.
The PR description’s Summary still mentions renaming a quickstart section (“The 6-Step Process” → “The 6-Step Workflow”), but this PR changes the installation command list and a grep pattern in local-development docs. Please update the PR description summary to match the actual changes (or include the referenced quickstart change in this PR).
|
Please address Copilot feedback |
Summary
"The 6-Step Workflow" for consistency with the rest
of the documentation
AI Disclosure
I did not use AI assistance for this contribution