Skip to content

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

refactor: remove OpenAPI/GraphQL bias from templates (#1652)

Manfred Riem12405c01e100
diff --git a/templates/commands/plan.md b/templates/commands/plan.md
index 147da0afa..00e83eabd 100644
--- a/templates/commands/plan.md
+++ b/templates/commands/plan.md
@@ -75,10 +75,11 @@ You **MUST** consider the user input before proceeding (if not empty).
- Validation rules from requirements
- State transitions if applicable
-2. **Generate API contracts** from functional requirements:
- - For each user action β†’ endpoint
- - Use standard REST/GraphQL patterns
- - Output OpenAPI/GraphQL schema to `/contracts/`
+2. **Define interface contracts** (if project has external interfaces) β†’ `/contracts/`:
+ - Identify what interfaces the project exposes to users or other systems
+ - Document the contract format appropriate for the project type
+ - Examples: public APIs for libraries, command schemas for CLI tools, endpoints for web services, grammars for parsers, UI contracts for applications
+ - Skip if project is purely internal (build scripts, one-off tools, etc.)
3. **Agent context update**:
- Run `{AGENT_SCRIPT}`
diff --git a/templates/commands/specify.md b/templates/commands/specify.md
index 3c952d683..5fd4489ee 100644
--- a/templates/commands/specify.md
+++ b/templates/commands/specify.md
@@ -235,7 +235,7 @@ When creating this spec from a user prompt:
- Performance targets: Standard web/mobile app expectations unless specified
- Error handling: User-friendly messages with appropriate fallbacks
- Authentication method: Standard session-based or OAuth2 for web apps
-- Integration patterns: RESTful APIs unless specified otherwise
+- Integration patterns: Use project-appropriate patterns (REST/GraphQL for web services, function calls for libraries, CLI args for tools, etc.)
### Success Criteria Guidelines
diff --git a/templates/commands/tasks.md b/templates/commands/tasks.md
index d69d43763..7320b6f30 100644
--- a/templates/commands/tasks.md
+++ b/templates/commands/tasks.md
@@ -28,14 +28,14 @@ You **MUST** consider the user input before proceeding (if not empty).
2. **Load design documents**: Read from FEATURE_DIR:
- **Required**: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
- - **Optional**: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
+ - **Optional**: data-model.md (entities), contracts/ (interface contracts), research.md (decisions), quickstart.md (test scenarios)
- Note: Not all projects have all documents. Generate tasks based on what's available.
3. **Execute task generation workflow**:
- Load plan.md and extract tech stack, libraries, project structure
- Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
- If data-model.md exists: Extract entities and map to user stories
- - If contracts/ exists: Map endpoints to user stories
+ - If contracts/ exists: Map interface contracts to user stories
- If research.md exists: Extract decisions for setup tasks
- Generate tasks organized by user story (see Task Generation Rules below)
- Generate dependency graph showing user story completion order
@@ -112,13 +112,13 @@ Every task MUST strictly follow this format:
- Map all related components to their story:
- Models needed for that story
- Services needed for that story
- - Endpoints/UI needed for that story
+ - Interfaces/UI needed for that story
- If tests requested: Tests specific to that story
- Mark story dependencies (most stories should be independent)
2. **From Contracts**:
- - Map each contract/endpoint β†’ to the user story it serves
- - If tests requested: Each contract β†’ contract test task [P] before implementation in that story's phase
+ - Map each interface contract β†’ to the user story it serves
+ - If tests requested: Each interface contract β†’ contract test task [P] before implementation in that story's phase
3. **From Data Model**:
- Map each entity to the user story(ies) that need it
diff --git a/templates/plan-template.md b/templates/plan-template.md
index dd47efceb..5a2fafebe 100644
--- a/templates/plan-template.md
+++ b/templates/plan-template.md
@@ -22,7 +22,7 @@
**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]
**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]
**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
-**Project Type**: [single/web/mobile - determines source structure]
+**Project Type**: [e.g., library/cli/web-service/mobile-app/compiler/desktop-app or NEEDS CLARIFICATION]
**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]
**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]
**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]