sdd-flow 1.0.0 → 1.2.4

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.
@@ -1,25 +1,25 @@
1
- #!/bin/bash
2
- # guard-deps.sh
3
- # Asks for confirmation before installing new packages.
4
- # Reinforces R08: no new dependency without justification in DECISIONS.md.
5
- # Exit 0 = allow | Exit 2 = block (Claude Code convention)
6
-
7
- INPUT=$(cat)
8
-
9
- COMMAND=$(echo "$INPUT" | grep -o '"command":"[^"]*"' | head -1 | sed 's/"command":"//;s/"//')
10
-
11
- # Intercept install commands that add NEW packages (not bare installs like "npm install" with no args)
12
- if echo "$COMMAND" | grep -qE "^(npm install|npm i|yarn add|pnpm add|bun add) .+" || \
13
- echo "$COMMAND" | grep -qE "^(pip install|pip3 install|uv add) .+"; then
14
- echo "⚠️ Agent wants to install a new dependency: $COMMAND" >&2
15
- echo " Remember: R08 requires justification in DECISIONS.md before adding packages." >&2
16
- read -r -p "Allow? [y/N] " response < /dev/tty
17
- if [[ "$response" =~ ^[Yy]$ ]]; then
18
- exit 0
19
- else
20
- echo "Blocked by guard-deps.sh" >&2
21
- exit 2
22
- fi
23
- fi
24
-
1
+ #!/bin/bash
2
+ # guard-deps.sh
3
+ # Asks for confirmation before installing new packages.
4
+ # Reinforces R08: no new dependency without justification in DECISIONS.md.
5
+ # Exit 0 = allow | Exit 2 = block (Claude Code convention)
6
+
7
+ INPUT=$(cat)
8
+
9
+ COMMAND=$(echo "$INPUT" | grep -o '"command":"[^"]*"' | head -1 | sed 's/"command":"//;s/"//')
10
+
11
+ # Intercept install commands that add NEW packages (not bare installs like "npm install" with no args)
12
+ if echo "$COMMAND" | grep -qE "^(npm install|npm i|yarn add|pnpm add|bun add) .+" || \
13
+ echo "$COMMAND" | grep -qE "^(pip install|pip3 install|uv add) .+"; then
14
+ echo "⚠️ Agent wants to install a new dependency: $COMMAND" >&2
15
+ echo " Remember: R08 requires justification in DECISIONS.md before adding packages." >&2
16
+ read -r -p "Allow? [y/N] " response < /dev/tty
17
+ if [[ "$response" =~ ^[Yy]$ ]]; then
18
+ exit 0
19
+ else
20
+ echo "Blocked by guard-deps.sh" >&2
21
+ exit 2
22
+ fi
23
+ fi
24
+
25
25
  exit 0
@@ -1,24 +1,24 @@
1
- #!/bin/bash
2
- # guard-git.sh
3
- # Asks for confirmation before running git commit.
4
- # git push, tag and branch -d are blocked via permissions.deny in settings.json.
5
- # Exit 0 = allow | Exit 2 = block (Claude Code convention)
6
-
7
- INPUT=$(cat)
8
-
9
- # Extract the bash command from the JSON input sent by Claude Code
10
- COMMAND=$(echo "$INPUT" | grep -o '"command":"[^"]*"' | head -1 | sed 's/"command":"//;s/"//')
11
-
12
- # Intercept only git commit
13
- if echo "$COMMAND" | grep -qE "^git commit"; then
14
- echo "⚠️ Agent wants to run: $COMMAND" >&2
15
- read -r -p "Allow git commit? [y/N] " response < /dev/tty
16
- if [[ "$response" =~ ^[Yy]$ ]]; then
17
- exit 0
18
- else
19
- echo "Blocked by guard-git.sh" >&2
20
- exit 2
21
- fi
22
- fi
23
-
1
+ #!/bin/bash
2
+ # guard-git.sh
3
+ # Asks for confirmation before running git commit.
4
+ # git push, tag and branch -d are blocked via permissions.deny in settings.json.
5
+ # Exit 0 = allow | Exit 2 = block (Claude Code convention)
6
+
7
+ INPUT=$(cat)
8
+
9
+ # Extract the bash command from the JSON input sent by Claude Code
10
+ COMMAND=$(echo "$INPUT" | grep -o '"command":"[^"]*"' | head -1 | sed 's/"command":"//;s/"//')
11
+
12
+ # Intercept only git commit
13
+ if echo "$COMMAND" | grep -qE "^git commit"; then
14
+ echo "⚠️ Agent wants to run: $COMMAND" >&2
15
+ read -r -p "Allow git commit? [y/N] " response < /dev/tty
16
+ if [[ "$response" =~ ^[Yy]$ ]]; then
17
+ exit 0
18
+ else
19
+ echo "Blocked by guard-git.sh" >&2
20
+ exit 2
21
+ fi
22
+ fi
23
+
24
24
  exit 0
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-implement.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-implement.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-plan.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-plan.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-research.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-research.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-validate.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-validate.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-implement.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-implement.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-plan.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-plan.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-research.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-research.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,3 +1,3 @@
1
- Read and follow `agents/prompts/rpi-validate.md`.
2
-
3
- Spec: $ARGUMENTS
1
+ Read and follow `agents/prompts/rpi-validate.md`.
2
+
3
+ Spec: $ARGUMENTS
@@ -1,46 +1,46 @@
1
- # Prompt: Implement (RPI — Phase 3)
2
-
3
- Use this prompt to implement a single task from an existing spec.
4
-
5
- ---
6
-
7
- ## Agent instruction
8
-
9
- You will implement **one single task** from an already planned feature.
10
-
11
- **Before starting, read:**
12
- - `agents/AGENTS.md`
13
- - `agents/PROJECT.md`
14
- - `agents/RULES.md`
15
- - `agents/specs/NNN-name/SPEC.md`
16
- - `agents/specs/NNN-name/TASK.md` — identify the first unchecked `[ ]`
17
- - `agents/specs/NNN-name/PROGRESS.md`
18
- - Run `grep -A 8 "## When to use" agents/skills/*/SKILL.md` — load the full `SKILL.md` only for skills relevant to this task
19
-
20
- **Expected input:**
21
- - Spec number (e.g. `001`)
22
- - Task to implement (e.g. `T03`) — if not provided, use the first unchecked `[ ]`
23
-
24
- ---
25
-
26
- ## Expected behavior
27
-
28
- 1. Declare which task will be implemented before generating any code
29
- 2. Implement only what is necessary for that single task
30
- 3. State exactly **which file** was created or modified
31
- 4. After completing:
32
- - Confirm the `verify:` condition on the completed task is met before marking it done
33
- - Mark `[x]` on the task in TASK.md
34
- - Update PROGRESS.md with what was done and any observations
35
- - Record relevant architectural decisions in DECISIONS.md
36
- 5. **Stop and wait for confirmation** before moving to the next task
37
-
38
- ---
39
-
40
- ## Constraints
41
-
42
- - Do not anticipate future tasks
43
- - Do not refactor code outside the current task's scope
44
- - Do not add dependencies without recording them in DECISIONS.md
45
- - Do not run git commands
46
- - If there is ambiguity about scope or approach, **ask before generating code**
1
+ # Prompt: Implement (RPI — Phase 3)
2
+
3
+ Use this prompt to implement a single task from an existing spec.
4
+
5
+ ---
6
+
7
+ ## Agent instruction
8
+
9
+ You will implement **one single task** from an already planned feature.
10
+
11
+ **Before starting, read:**
12
+ - `agents/AGENTS.md`
13
+ - `agents/PROJECT.md`
14
+ - `agents/RULES.md`
15
+ - `agents/specs/NNN-name/SPEC.md`
16
+ - `agents/specs/NNN-name/TASK.md` — identify the first unchecked `[ ]`
17
+ - `agents/specs/NNN-name/PROGRESS.md`
18
+ - Run `grep -A 8 "## When to use" agents/skills/*/SKILL.md` — load the full `SKILL.md` only for skills relevant to this task
19
+
20
+ **Expected input:**
21
+ - Spec number (e.g. `001`)
22
+ - Task to implement (e.g. `T03`) — if not provided, use the first unchecked `[ ]`
23
+
24
+ ---
25
+
26
+ ## Expected behavior
27
+
28
+ 1. Declare which task will be implemented before generating any code
29
+ 2. Implement only what is necessary for that single task
30
+ 3. State exactly **which file** was created or modified
31
+ 4. After completing:
32
+ - Confirm the `verify:` condition on the completed task is met before marking it done
33
+ - Mark `[x]` on the task in TASK.md
34
+ - Update PROGRESS.md with what was done and any observations
35
+ - Record relevant architectural decisions in DECISIONS.md
36
+ 5. **Stop and wait for confirmation** before moving to the next task
37
+
38
+ ---
39
+
40
+ ## Constraints
41
+
42
+ - Do not anticipate future tasks
43
+ - Do not refactor code outside the current task's scope
44
+ - Do not add dependencies without recording them in DECISIONS.md
45
+ - Do not run git commands
46
+ - If there is ambiguity about scope or approach, **ask before generating code**
@@ -1,117 +1,117 @@
1
- # Prompt: Plan (RPI — Phase 2)
2
-
3
- Use this prompt to generate all planning artifacts for a spec.
4
-
5
- ---
6
-
7
- ## Agent instruction
8
-
9
- You will plan the implementation of an already-researched feature.
10
-
11
- **Before starting, read:**
12
- - `agents/AGENTS.md`
13
- - `agents/PROJECT.md`
14
- - `agents/RULES.md`
15
- - `agents/specs/NNN-name/RESEARCH.md`
16
- - Check which files already exist in `agents/specs/NNN-name/`
17
-
18
- **Expected input:**
19
- - Spec number and name (e.g. `001-user-authentication`)
20
-
21
- ---
22
-
23
- ## Adaptive behavior
24
-
25
- | Situation | Action |
26
- |---|---|
27
- | SPEC.md does not exist | Create all artifacts from scratch |
28
- | SPEC.md exists, TASK.md does not | Generate only TASK.md and PROGRESS.md based on existing SPEC.md |
29
- | All artifacts exist | Review and update only what is incomplete or outdated |
30
-
31
- ---
32
-
33
- ## Deliverables
34
-
35
- Generate the following files inside `agents/specs/NNN-name/`:
36
-
37
- ### SPEC.md
38
- ```markdown
39
- # SPEC — [Feature Name]
40
-
41
- ## Goal
42
- What this feature delivers (refined from RESEARCH.md).
43
-
44
- ## Entities involved
45
- Data structures created or modified, with full field list.
46
-
47
- ## Business Rules
48
- Numbered list. Only rules that directly affect implementation.
49
-
50
- ## Expected behaviors
51
- Per behavior: what triggers it, what it does, what the output is.
52
-
53
- ## UI
54
- Describe components, states, interactions and validations.
55
- Write `N/A` if no UI is involved.
56
-
57
- ## Out of scope
58
- Explicit list of what this spec does NOT cover.
59
- ```
60
-
61
- ### TASK.md
62
- ```markdown
63
- # TASK — [Feature Name]
64
-
65
- ## Tasks
66
-
67
- - [ ] T01 — [Verb + object + target file] (e.g. Create User entity schema in config)
68
- verify: [observable condition confirming completion — e.g. endpoint returns 201 with `id` field; returns 400 if `email` is missing]
69
- - [ ] T02 — ...
70
- verify: [specific and testable condition — never "works correctly"]
71
- ```
72
-
73
- Task rules:
74
- - One task = one file created/modified, or one isolated function
75
- - Order must respect dependencies (schema → data layer → service → route → UI)
76
- - No circular dependencies between tasks
77
- - Preferred verbs: `Add`, `Create`, `Implement`, `Update`, `Extract`, `Register`
78
- - Each task must include a `verify:` line with a specific, observable condition — never "works correctly"
79
-
80
- ### PROGRESS.md
81
- ```markdown
82
- # PROGRESS — [Feature Name]
83
-
84
- ## Status: 🔴 Not started
85
-
86
- ## Tasks
87
-
88
- | Task | Status | Notes |
89
- |---|---|---|
90
- | T01 | Pending | |
91
- | T02 | Pending | |
92
-
93
- ## History
94
-
95
- (updated during implementation)
96
- ```
97
-
98
- ### TEST.md
99
- ```markdown
100
- # TEST — [Feature Name]
101
-
102
- ## Acceptance Test Cases
103
-
104
- ### TC01 — [Behavior being tested]
105
- - **Given** [initial state]
106
- - **When** [action performed]
107
- - **Then** [expected outcome]
108
- ```
109
-
110
- ---
111
-
112
- ## Constraints
113
-
114
- - Do not write code in this phase
115
- - Do not implement any task — only plan
116
- - If the RESEARCH.md has unresolved open questions, **stop and ask** before planning
117
- - After delivering all artifacts, **wait for approval** before advancing to Implement
1
+ # Prompt: Plan (RPI — Phase 2)
2
+
3
+ Use this prompt to generate all planning artifacts for a spec.
4
+
5
+ ---
6
+
7
+ ## Agent instruction
8
+
9
+ You will plan the implementation of an already-researched feature.
10
+
11
+ **Before starting, read:**
12
+ - `agents/AGENTS.md`
13
+ - `agents/PROJECT.md`
14
+ - `agents/RULES.md`
15
+ - `agents/specs/NNN-name/RESEARCH.md`
16
+ - Check which files already exist in `agents/specs/NNN-name/`
17
+
18
+ **Expected input:**
19
+ - Spec number and name (e.g. `001-user-authentication`)
20
+
21
+ ---
22
+
23
+ ## Adaptive behavior
24
+
25
+ | Situation | Action |
26
+ |---|---|
27
+ | SPEC.md does not exist | Create all artifacts from scratch |
28
+ | SPEC.md exists, TASK.md does not | Generate only TASK.md and PROGRESS.md based on existing SPEC.md |
29
+ | All artifacts exist | Review and update only what is incomplete or outdated |
30
+
31
+ ---
32
+
33
+ ## Deliverables
34
+
35
+ Generate the following files inside `agents/specs/NNN-name/`:
36
+
37
+ ### SPEC.md
38
+ ```markdown
39
+ # SPEC — [Feature Name]
40
+
41
+ ## Goal
42
+ What this feature delivers (refined from RESEARCH.md).
43
+
44
+ ## Entities involved
45
+ Data structures created or modified, with full field list.
46
+
47
+ ## Business Rules
48
+ Numbered list. Only rules that directly affect implementation.
49
+
50
+ ## Expected behaviors
51
+ Per behavior: what triggers it, what it does, what the output is.
52
+
53
+ ## UI
54
+ Describe components, states, interactions and validations.
55
+ Write `N/A` if no UI is involved.
56
+
57
+ ## Out of scope
58
+ Explicit list of what this spec does NOT cover.
59
+ ```
60
+
61
+ ### TASK.md
62
+ ```markdown
63
+ # TASK — [Feature Name]
64
+
65
+ ## Tasks
66
+
67
+ - [ ] T01 — [Verb + object + target file] (e.g. Create User entity schema in config)
68
+ verify: [observable condition confirming completion — e.g. endpoint returns 201 with `id` field; returns 400 if `email` is missing]
69
+ - [ ] T02 — ...
70
+ verify: [specific and testable condition — never "works correctly"]
71
+ ```
72
+
73
+ Task rules:
74
+ - One task = one file created/modified, or one isolated function
75
+ - Order must respect dependencies (schema → data layer → service → route → UI)
76
+ - No circular dependencies between tasks
77
+ - Preferred verbs: `Add`, `Create`, `Implement`, `Update`, `Extract`, `Register`
78
+ - Each task must include a `verify:` line with a specific, observable condition — never "works correctly"
79
+
80
+ ### PROGRESS.md
81
+ ```markdown
82
+ # PROGRESS — [Feature Name]
83
+
84
+ ## Status: 🔴 Not started
85
+
86
+ ## Tasks
87
+
88
+ | Task | Status | Notes |
89
+ |---|---|---|
90
+ | T01 | Pending | |
91
+ | T02 | Pending | |
92
+
93
+ ## History
94
+
95
+ (updated during implementation)
96
+ ```
97
+
98
+ ### TEST.md
99
+ ```markdown
100
+ # TEST — [Feature Name]
101
+
102
+ ## Acceptance Test Cases
103
+
104
+ ### TC01 — [Behavior being tested]
105
+ - **Given** [initial state]
106
+ - **When** [action performed]
107
+ - **Then** [expected outcome]
108
+ ```
109
+
110
+ ---
111
+
112
+ ## Constraints
113
+
114
+ - Do not write code in this phase
115
+ - Do not implement any task — only plan
116
+ - If the RESEARCH.md has unresolved open questions, **stop and ask** before planning
117
+ - After delivering all artifacts, **wait for approval** before advancing to Implement