speckit-implement-zh

User Input

text

$ARGUMENTS

You must consider the user input (if not empty) before proceeding.

Outline

scripts: sh: .specify/scripts/bash/check-prerequisites.sh --json ps: .specify/scripts/powershell/check-prerequisites.ps1 -Json

Run
```
{SCRIPT}
```
from the root directory of the repository and parse the FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in parameters, such as "I'm Groot", use escape syntax: for example 'I'''m Groot' (or use double quotes if possible: "I'm Groot").
Check Checklist Status (if FEATURE_DIR/checklists/ exists):
- Scan all checklist files in the checklists/ directory
- For each checklist, count:
  - Total items: All lines matching
    - [ ]
    or
    - [X]
    or
    - [x]
  - Completed items: Lines matching
    - [X]
    or
    - [x]
  - Incomplete items: Lines matching
    - [ ]
- Create a status table:
  text
```
| Checklist | Total | Completed | Incomplete | Status |
|-----------|-------|-----------|------------|--------|
| ux.md     | 12    | 12        | 0          | ✓ Pass |
| test.md   | 8     | 5         | 3          | ✗ Fail |
| security.md | 6   | 6         | 0          | ✓ Pass |
```
- Calculate overall status:
  - Pass: All checklists have 0 incomplete items
  - Fail: One or more checklists have incomplete items
- If any checklist is incomplete:
  - Display the table with the count of incomplete items
  - Stop and ask: "Some checklists are incomplete. Do you still want to proceed with the implementation? (yes/no)"
  - Wait for user response before continuing
  - Stop execution if the user says "no", "wait", or "stop"
  - Proceed to step 3 if the user says "yes", "proceed", or "continue"
- If all checklists are completed:
  - Display the table showing all checklists have passed
  - Automatically proceed to step 3
Load and analyze implementation context:
- Required: Read tasks.md to get the complete task list and execution plan
- Required: Read plan.md to get the tech stack, architecture, and file structure
- If exists: Read data-model.md to get entities and relationships
- If exists: Read contracts/ to get API specifications and testing requirements
- If exists: Read research.md to get technical decisions and constraints
- If exists: Read quickstart.md to get integration scenarios
Project Setup Verification:
- Required: Create/verify ignore files based on actual project setup:
Detection and Creation Logic:
- Check if the following command succeeds to determine if the repository is a git repository (create/verify .gitignore if yes):
  sh
```
git rev-parse --git-dir 2>/dev/null
```
- Check if Dockerfile* exists or Docker is mentioned in plan.md → create/verify .dockerignore
- Check if .eslintrc* or eslint.config.* exists → create/verify .eslintignore
- Check if .prettierrc* exists → create/verify .prettierignore
- Check if .npmrc or package.json exists → create/verify .npmignore (if publishing)
- Check if terraform files (*.tf) exist → create/verify .terraformignore
- Check if .helmignore is needed (helm charts exist) → create/verify .helmignore
If ignore files already exist: Verify that they contain basic patterns, only append missing critical patterns If ignore files are missing: Create a complete set of patterns based on detected technologies

Common Patterns by Technology (from plan.md tech stack):
- Node.js/JavaScript/TypeScript:
```
node_modules/
```
  ,
```
dist/
```
  ,
```
build/
```
  ,
```
*.log
```
  ,
```
.env*
```
- Python:
```
__pycache__/
```
  ,
```
*.pyc
```
  ,
```
.venv/
```
  ,
```
venv/
```
  ,
```
dist/
```
  ,
```
*.egg-info/
```
- Java:
```
target/
```
  ,
```
*.class
```
  ,
```
*.jar
```
  ,
```
.gradle/
```
  ,
```
build/
```
- C#/.NET:
```
bin/
```
  ,
```
obj/
```
  ,
```
*.user
```
  ,
```
*.suo
```
  ,
```
packages/
```
- Go:
```
*.exe
```
  ,
```
*.test
```
  ,
```
vendor/
```
  ,
```
*.out
```
- Ruby:
```
.bundle/
```
  ,
```
log/
```
  ,
```
tmp/
```
  ,
```
*.gem
```
  ,
```
vendor/bundle/
```
- PHP:
```
vendor/
```
  ,
```
*.log
```
  ,
```
*.cache
```
  ,
```
*.env
```
- Rust:
```
target/
```
  ,
```
debug/
```
  ,
```
release/
```
  ,
```
*.rs.bk
```
  ,
```
*.rlib
```
  ,
```
*.prof*
```
  ,
```
.idea/
```
  ,
```
*.log
```
  ,
```
.env*
```
- Kotlin:
```
build/
```
  ,
```
out/
```
  ,
```
.gradle/
```
  ,
```
.idea/
```
  ,
```
*.class
```
  ,
```
*.jar
```
  ,
```
*.iml
```
  ,
```
*.log
```
  ,
```
.env*
```
- C++:
```
build/
```
  ,
```
bin/
```
  ,
```
obj/
```
  ,
```
out/
```
  ,
```
*.o
```
  ,
```
*.so
```
  ,
```
*.a
```
  ,
```
*.exe
```
  ,
```
*.dll
```
  ,
```
.idea/
```
  ,
```
*.log
```
  ,
```
.env*
```
- C:
```
build/
```
  ,
```
bin/
```
  ,
```
obj/
```
  ,
```
out/
```
  ,
```
*.o
```
  ,
```
*.a
```
  ,
```
*.so
```
  ,
```
*.exe
```
  ,
```
Makefile
```
  ,
```
config.log
```
  ,
```
.idea/
```
  ,
```
*.log
```
  ,
```
.env*
```
- Swift:
```
.build/
```
  ,
```
DerivedData/
```
  ,
```
*.swiftpm/
```
  ,
```
Packages/
```
- R:
```
.Rproj.user/
```
  ,
```
.Rhistory
```
  ,
```
.RData
```
  ,
```
.Ruserdata
```
  ,
```
*.Rproj
```
  ,
```
packrat/
```
  ,
```
renv/
```
- General:
```
.DS_Store
```
  ,
```
Thumbs.db
```
  ,
```
*.tmp
```
  ,
```
*.swp
```
  ,
```
.vscode/
```
  ,
```
.idea/
```
Tool-Specific Patterns:
- Docker:
```
node_modules/
```
  ,
```
.git/
```
  ,
```
Dockerfile*
```
  ,
```
.dockerignore
```
  ,
```
*.log*
```
  ,
```
.env*
```
  ,
```
coverage/
```
- ESLint:
```
node_modules/
```
  ,
```
dist/
```
  ,
```
build/
```
  ,
```
coverage/
```
  ,
```
*.min.js
```
- Prettier:
```
node_modules/
```
  ,
```
dist/
```
  ,
```
build/
```
  ,
```
coverage/
```
  ,
```
package-lock.json
```
  ,
```
yarn.lock
```
  ,
```
pnpm-lock.yaml
```
- Terraform:
```
.terraform/
```
  ,
```
*.tfstate*
```
  ,
```
*.tfvars
```
  ,
```
.terraform.lock.hcl
```
- Kubernetes/k8s:
```
*.secret.yaml
```
  ,
```
secrets/
```
  ,
```
.kube/
```
  ,
```
kubeconfig*
```
  ,
```
*.key
```
  ,
```
*.crt
```
Parse tasks.md structure and extract:
- Task Phases: Setup, Testing, Core, Integration, Polish
- Task Dependencies: Sequential and parallel execution rules
- Task Details: ID, description, file path, parallel marker [P]
- Execution Flow: Sequential and dependency requirements
Execute implementation according to the task plan:
- Phase Execution: Complete each phase before moving to the next
- Respect Dependencies: Run sequential tasks in order, parallel tasks marked [P] can be run together
- Follow TDD Approach: Execute testing tasks before corresponding implementation tasks
- File-Based Coordination: Tasks affecting the same file must be run sequentially
- Validation Checkpoints: Verify completion of each phase before proceeding
Implementation Execution Rules:
- Setup First: Initialize project structure, dependencies, configuration
- Tests Before Code: Write tests for contracts, entities, and integration scenarios if needed
- Core Development: Implement models, services, CLI commands, endpoints
- Integration Work: Database connections, middleware, logging, external services
- Polish and Validation: Unit tests, performance optimization, documentation
Progress Tracking and Error Handling:
- Report progress after each completed task
- Stop execution if any non-parallel task fails
- For parallel tasks marked [P], continue with successful tasks and report failed ones
- Provide clear error messages and debugging context
- Suggest next steps if implementation cannot proceed
- Important: For completed tasks, ensure they are marked as [X] in the task file.
Completion Verification:
- Verify all required tasks are completed
- Check if implemented features match the original specifications
- Verify tests pass and coverage meets requirements
- Confirm implementation follows the technical plan
- Report final status and a summary of completed work

Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, it is recommended to first run

speckit-tasks

to regenerate the task list.

speckit-implement-zh

NPX Install

Tags

SKILL.md Content (Chinese)

User Input

Outline