Skip to content

πŸ’« Toolkit to help you get started with SDD or any other process!

revert vscode auto remove extra space

danielshihe0e62f675798
diff --git a/templates/commands/implement.md b/templates/commands/implement.md
index 9a804a0b6..8e19caf90 100644
--- a/templates/commands/implement.md
+++ b/templates/commands/implement.md
@@ -34,14 +34,14 @@ You **MUST** consider the user input before proceeding (if not empty).
- 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 incomplete item counts
* **STOP** and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
* Wait for user response before continuing
* If user says "no" or "wait" or "stop", halt execution
* If user says "yes" or "proceed" or "continue", proceed to step 3
-
+
- **If all checklists are complete**:
* Display the table showing all checklists passed
* Automatically proceed to step 3
@@ -56,7 +56,7 @@ You **MUST** consider the user input before proceeding (if not empty).
4. **Project Setup Verification**:
- **REQUIRED**: Create/verify ignore files based on actual project setup:
-
+
**Detection & Creation Logic**:
- Check if the following command succeeds to determine if the repository is a git repo (create/verify .gitignore if so):
@@ -69,10 +69,10 @@ You **MUST** consider the user input before proceeding (if not empty).
- Check if .npmrc or package.json exists β†’ create/verify .npmignore (if publishing)
- Check if terraform files (*.tf) exist β†’ create/verify .terraformignore
- Check if .helmignore needed (helm charts present) β†’ create/verify .helmignore
-
+
**If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
**If ignore file missing**: Create with full pattern set for detected technology
-
+
**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/`
@@ -88,7 +88,7 @@ You **MUST** consider the user input before proceeding (if not empty).
- **Swift**: `.build/`, `DerivedData/`, `*.swiftpm/`, `Packages/`
- **R**: `.Rproj.user/`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat/`, `renv/`
- **Universal**: `.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`
@@ -104,7 +104,7 @@ You **MUST** consider the user input before proceeding (if not empty).
6. Execute implementation following the task plan:
- **Phase-by-phase execution**: Complete each phase before moving to the next
- - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
+ - **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
- **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
- **File-based coordination**: Tasks affecting the same files must run sequentially
- **Validation checkpoints**: Verify each phase completion before proceeding