Skip to content

update section title from Process to Workflow in quickstart guide #2254

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
HumaizaNaz wants to merge 6 commits into
base: main
Choose a base branch
from
+7 −5
Open

update section title from Process to Workflow in quickstart guide #2254

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
9f7bc34
Update section title from 'Process' to 'Workflow'
HumaizaNaz Apr 17, 2026
342b1ba
Merge pull request #1 from HumaizaNaz/HumaizaNaz-patch-1
HumaizaNaz Apr 17, 2026
0caab6e
Update installation instructions with new commands
HumaizaNaz Apr 17, 2026
1004c06
Merge pull request #2 from HumaizaNaz/HumaizaNaz-patch-2
HumaizaNaz Apr 17, 2026
156f08e
Fix grep pattern for shell script check
HumaizaNaz Apr 17, 2026
52604a9
Merge pull request #3 from HumaizaNaz/HumaizaNaz-patch-3
HumaizaNaz Apr 17, 2026
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
8 changes: 5 additions & 3 deletions docs/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,9 +81,11 @@ This helps verify you are running the official Spec Kit build from GitHub, not a

After initialization, you should see the following commands available 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

The `.specify/scripts` directory will contain both `.sh` and `.ps1` scripts.

Expand Down
2 changes: 1 addition & 1 deletion docs/local-development.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ specify-dev --help
After running an `init`, check that shell scripts are executable on POSIX systems:

```bash
ls -l scripts | grep .sh
ls -l scripts | grep '\.sh'
# Expect owner execute bit (e.g. -rwxr-xr-x)
```

Expand Down
2 changes: 1 addition & 1 deletion docs/quickstart.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ This guide will help you get started with Spec-Driven Development using Spec Kit
> [!NOTE]
> All automation scripts now provide both Bash (`.sh`) and PowerShell (`.ps1`) variants. The `specify` CLI auto-selects based on OS unless you pass `--script sh|ps`.

## The 6-Step Process
Copy link
Copy Markdown
Collaborator

@mnriem mnriem Apr 17, 2026

Choose a reason for hiding this comment

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

As we have Spec Kit workflows this MUST stay Process.

## The 6-Step Workflow

> [!TIP]
> **Context Awareness**: Spec Kit commands automatically detect the active feature based on your current Git branch (e.g., `001-feature-name`). To switch between different specifications, simply switch Git branches.
Expand Down