Files
skeleton/.codex/prompts/requirements.md
Worker Skeletton 5c9b4333da Unify OpenCode and Codex starter kits
- Add .shared/prompts/ with tool-neutral prompts
- Add .opencode/config/project.md, rules/, skills/ from opencode-kit
- Add .codex/config/project.md from codex-kit
- Copy .shared/prompts/ to both .opencode/prompts/ and .codex/prompts/
- Add features/INDEX.md and features/README.md
- Update README with unified structure

The two original starter kits are now redundant.
2026-05-25 14:11:00 +02:00

25 lines
1023 B
Markdown

# Requirements Prompt Template
Use this prompt structure for creating feature specifications:
```
Read docs/<domain>/doku/PRD.md to understand the project vision and constraints.
Read features/INDEX.md to see existing features and the next available PROJ-X ID.
[Describe the feature idea clearly]
Create a feature specification in features/PROJ-X-feature-name.md with:
- Feature name and ID
- User stories (3-5, with: As a [role], I want [action], so that [benefit])
- Acceptance criteria (testable, specific)
- Edge cases (error handling, edge inputs, boundary conditions)
- Dependencies (other features required)
- Implementation notes (optional)
Update features/INDEX.md with the new feature status.
```
Example:
```
<ai-tool> exec "Read docs/www.example.com/doku/PRD.md and features/INDEX.md. Create a feature spec for user authentication with email/password login, including: user stories for login/logout, acceptance criteria for valid/invalid credentials, edge cases for locked accounts and rate limiting."
```