Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs: clarify Taskify specify command#3016

Open
Jiandong7 wants to merge 1 commit into
github:mainfrom
Jiandong7:docs/472-quickstart-taskify-command
Open

docs: clarify Taskify specify command#3016
Jiandong7 wants to merge 1 commit into
github:mainfrom
Jiandong7:docs/472-quickstart-taskify-command

Conversation

@Jiandong7

Copy link
Copy Markdown

Summary

  • Clarify the Taskify quickstart example by including the /speckit.specify command directly in the requirements prompt.
  • Keeps the detailed example consistent with the rest of the quickstart, where each chat action shows the full slash command users should enter.

Fixes #472.

Test plan

  • npx --yes markdownlint-cli2 docs/quickstart.md
  • git diff --check

AI disclosure

This PR was prepared with assistance from Codex on behalf of @Jiandong7. The change was verified locally with the checks above.

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

This PR updates the Taskify “Detailed Example” in the quickstart to remove ambiguity about how to invoke the requirements step by embedding the full /speckit.specify slash command directly into the example prompt.

Changes:

  • Updates the Step 2 requirements example so the first line starts with /speckit.specify, making it clear the command and prompt are entered together.
Show a summary per file
File Description
docs/quickstart.md Adjusts the Taskify Step 2 example to include /speckit.specify inline with the requirements prompt for clarity and consistency.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

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.

Docs issues

3 participants