sheldon/loop-loop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: remove domain-specific language from prompts — fully universal

Browse Source
This commit is contained in:
Sheldon Finlay
2026-03-27 14:50:52 -04:00
parent 48bc656cd8
commit f3cbfd258c
2 changed files with 19 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
prompts/generator/implement.md
View File

@@ -2,36 +2,25 @@
You are building features from a PRD. Each story is a small, self-contained unit of work.
## Implementation Workflow
## Workflow
1. Read the story's acceptance criteria carefully — these are your definition of done
1. Read the story's acceptance criteria — these are your definition of done
2. If a sprint contract exists, follow its **Done Conditions** exactly
3. Plan your approach before writing code:
- What files need to change?
- What existing code can you reuse?
- What's the minimal change to satisfy the criteria?
3. Plan: what files need to change? What existing code can you reuse? What's the minimal change?
4. Implement the story
5. Run quality gates (typecheck, lint, test)
6. Commit with a descriptive message
7. Mark the story as passed
5. Run quality gates (typecheck, lint, test — whatever the project uses)
6. Verify it actually works — build it, run it, test it
7. Commit and mark as passed
## Constraints
- **Minimal changes only.** Do not refactor surrounding code. Do not add features beyond the story scope.
- **Follow the contract's Out of Scope section** — do not implement anything listed there.
- **If tests don't exist yet,** write them as part of the story (unless the story is specifically about something else and testing is a separate story).
- **If you need a dependency,** install it and note it in progress.md so future iterations know.
- **Minimal changes only.** Do not refactor surrounding code or add features beyond scope.
- **Follow the contract's Out of Scope section.**
- **If tests don't exist yet,** write them as part of the story.
- **If you need a dependency,** install it and note it in progress.md.
## Browser Verification (UI Stories)
## Git
For stories that change user-facing UI:
- Use browser verification tools if available (Puppeteer MCP, dev-browser skill)
- Navigate to the affected page and verify the change works
- A UI story is NOT complete without visual verification
## Git Workflow
- Ensure you're on the branch specified in prd.json
- Stage only the files you changed (not `git add .`)
- Commit message: `feat: [Story ID] - [Story Title]`
- Do NOT push — the loop handles that