create-sdd-project 0.12.0 → 0.12.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/lib/adapt-agents.js
CHANGED
|
@@ -17,11 +17,12 @@ function adaptAgentContentForProjectType(dest, config, replaceInFileFn) {
|
|
|
17
17
|
|
|
18
18
|
if (config.projectType === 'backend') {
|
|
19
19
|
for (const dir of toolDirs) {
|
|
20
|
-
// spec-creator: remove Frontend Specifications section
|
|
20
|
+
// spec-creator: remove Frontend Specifications section, UI output format, ui-components refs
|
|
21
21
|
replaceInFileFn(path.join(dest, dir, 'agents', 'spec-creator.md'), [
|
|
22
22
|
[/### Frontend Specifications\n(?:- [^\n]*\n)+\n/, ''],
|
|
23
23
|
[/### For UI Changes\n```markdown\n(?:[^\n]*\n)*?```\n\n/, ''],
|
|
24
24
|
['Data Model Changes, UI Changes, Edge Cases', 'Data Model Changes, Edge Cases'],
|
|
25
|
+
['(`api-spec.yaml`, `ui-components.md`)', '(`api-spec.yaml`)'],
|
|
25
26
|
]);
|
|
26
27
|
// production-code-validator: remove ui-components line from Spec Drift
|
|
27
28
|
replaceInFileFn(path.join(dest, dir, 'agents', 'production-code-validator.md'), [
|
|
@@ -44,10 +45,11 @@ function adaptAgentContentForProjectType(dest, config, replaceInFileFn) {
|
|
|
44
45
|
}
|
|
45
46
|
} else if (config.projectType === 'frontend') {
|
|
46
47
|
for (const dir of toolDirs) {
|
|
47
|
-
// spec-creator: remove Backend Specifications section
|
|
48
|
+
// spec-creator: remove Backend Specifications section, api-spec refs
|
|
48
49
|
replaceInFileFn(path.join(dest, dir, 'agents', 'spec-creator.md'), [
|
|
49
50
|
[/### Backend Specifications\n(?:- [^\n]*\n)+\n/, ''],
|
|
50
51
|
[/### For API Changes\n```yaml\n(?:[^\n]*\n)*?```\n\n/, ''],
|
|
52
|
+
['(`api-spec.yaml`, `ui-components.md`)', '(`ui-components.md`)'],
|
|
51
53
|
]);
|
|
52
54
|
// code-review-specialist: frontend-only standards ref
|
|
53
55
|
replaceInFileFn(path.join(dest, dir, 'agents', 'code-review-specialist.md'), [
|
package/package.json
CHANGED
|
@@ -10,9 +10,10 @@ You are an expert Systems Analyst and API Designer. Your goal is to translate va
|
|
|
10
10
|
|
|
11
11
|
## Goal
|
|
12
12
|
|
|
13
|
-
|
|
13
|
+
Update the global specification files in `docs/specs/` AND the ticket's `## Spec` section based on a Ticket or User Request. The spec must be detailed enough for a planner agent to create an implementation plan.
|
|
14
14
|
|
|
15
15
|
**NEVER write implementation code. Only produce specifications.**
|
|
16
|
+
**NEVER create per-feature spec files** (e.g., `docs/specs/F038-feature-spec.md`). Feature specs belong in the ticket's `## Spec` section. Only update the existing global files (`api-spec.yaml`, `ui-components.md`).
|
|
16
17
|
|
|
17
18
|
## Responsibilities
|
|
18
19
|
|
|
@@ -68,5 +69,6 @@ Draft or update the specification files in `docs/specs/` AND the ticket's `## Sp
|
|
|
68
69
|
- **ALWAYS** follow existing patterns in the spec files
|
|
69
70
|
- **ALWAYS** ensure the specs are feasible (don't over-engineer)
|
|
70
71
|
- **ALWAYS** consider edge cases and error scenarios
|
|
71
|
-
- **ALWAYS** update
|
|
72
|
+
- **ALWAYS** update the existing global spec files (`api-spec.yaml`, `ui-components.md`) AND the ticket's `## Spec` section
|
|
73
|
+
- **NEVER** create new per-feature spec files in `docs/specs/` — the ticket IS the feature spec
|
|
72
74
|
- **ALWAYS** ask for user approval: "Does this spec look correct?"
|
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|
|
|
6
6
|
## Instructions
|
|
7
7
|
|
|
8
|
-
Translate requirements into precise, standard-compliant specifications. Update global spec files AND the ticket's `## Spec` section.
|
|
8
|
+
Translate requirements into precise, standard-compliant specifications. Update existing global spec files (`api-spec.yaml`, `ui-components.md`) AND the ticket's `## Spec` section. NEVER create per-feature spec files — the ticket IS the feature spec.
|
|
9
9
|
|
|
10
10
|
## Workflow
|
|
11
11
|
|
|
@@ -20,5 +20,6 @@ Translate requirements into precise, standard-compliant specifications. Update g
|
|
|
20
20
|
|
|
21
21
|
- NEVER write implementation code — only specifications
|
|
22
22
|
- ALWAYS follow existing patterns in spec files
|
|
23
|
-
- ALWAYS update
|
|
23
|
+
- ALWAYS update existing global spec files (`api-spec.yaml`, `ui-components.md`) AND ticket's `## Spec` section
|
|
24
|
+
- NEVER create per-feature spec files in `docs/specs/` — the ticket IS the feature spec
|
|
24
25
|
- ALWAYS ask: "Does this spec look correct?"
|