@llipe.com/dev-tasks 0.16.1 → 0.16.2
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/.claude/agents/developer.md +45 -31
- package/.claude/agents/technical-writer.md +11 -9
- package/.claude/agents/verifier.md +15 -0
- package/.claude/commands/planner.md +60 -12
- package/.claude/commands/product-engineer.md +54 -8
- package/.claude/hooks/git-guard.sh +151 -63
- package/.claude/skills/implement/SKILL.md +12 -8
- package/.claude/skills/memo-cli-usage/REFERENCE.md +11 -11
- package/.claude/skills/memo-cli-usage/SKILL.md +11 -9
- package/.github/agents/developer.agent.md +45 -31
- package/.github/agents/planner.agent.md +60 -12
- package/.github/agents/product-engineer.agent.md +54 -8
- package/.github/agents/technical-writer.agent.md +11 -9
- package/.github/agents/verifier.agent.md +15 -0
- package/.github/instructions/implement.instructions.md +12 -8
- package/.github/skills/memo-cli-usage/REFERENCE.md +11 -11
- package/.github/skills/memo-cli-usage/SKILL.md +11 -9
- package/.kiro/agents/developer.md +45 -31
- package/.kiro/agents/planner.md +60 -12
- package/.kiro/agents/product-engineer.md +54 -8
- package/.kiro/agents/technical-writer.md +11 -9
- package/.kiro/agents/verifier.md +15 -0
- package/.kiro/hooks/scripts/git-guard.sh +96 -10
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +11 -11
- package/.kiro/skills/memo-cli-usage/SKILL.md +11 -9
- package/.kiro/steering/implement.md +12 -8
- package/AGENTS.md +7 -5
- package/AGENTS.md.template +3 -1
- package/CHANGELOG.md +19 -0
- package/CLAUDE.md +2 -1
- package/CLAUDE.md.template +2 -1
- package/package.json +1 -1
|
@@ -54,13 +54,97 @@ block() {
|
|
|
54
54
|
exit 2
|
|
55
55
|
}
|
|
56
56
|
|
|
57
|
+
# Split the raw command into simple-command segments, one per output line,
|
|
58
|
+
# at `&&`, `||`, `;`, `|`, `&`, and newlines outside single or double quotes
|
|
59
|
+
# (backslash escapes honored). Every rule that reads a command's arguments
|
|
60
|
+
# reads them from its own segment, never from the rest of the string. Before
|
|
61
|
+
# this, `git push -u origin feat && gh pr create --base main` read `main` as
|
|
62
|
+
# a push destination, `--tags` anywhere in the string read as a tag push, and
|
|
63
|
+
# a greedy `.*git push` match checked only the LAST push in a chained
|
|
64
|
+
# command, so `git push origin main && git push origin feat` was allowed
|
|
65
|
+
# (issue #256). Portable awk only: macOS ships BSD awk, not gawk.
|
|
66
|
+
command_segments() {
|
|
67
|
+
printf '%s\n' "$cmd" | awk '
|
|
68
|
+
{ s = s (NR > 1 ? "\n" : "") $0 }
|
|
69
|
+
END {
|
|
70
|
+
out = ""; q = ""; n = length(s)
|
|
71
|
+
for (i = 1; i <= n; i++) {
|
|
72
|
+
c = substr(s, i, 1)
|
|
73
|
+
if (q != "") {
|
|
74
|
+
# Inside quotes a newline is part of the argument, never a
|
|
75
|
+
# separator: map it to a space so the segment stays whole.
|
|
76
|
+
if (c == "\n") { out = out " "; continue }
|
|
77
|
+
if (c == q) { q = ""; out = out c; continue }
|
|
78
|
+
if (c == "\\" && q == "\"" && i < n) {
|
|
79
|
+
d = substr(s, i + 1, 1); i++
|
|
80
|
+
if (d != "\n") out = out c d # backslash-newline is a continuation
|
|
81
|
+
continue
|
|
82
|
+
}
|
|
83
|
+
out = out c
|
|
84
|
+
continue
|
|
85
|
+
}
|
|
86
|
+
if (c == "\\" && i < n) {
|
|
87
|
+
d = substr(s, i + 1, 1); i++
|
|
88
|
+
if (d != "\n") out = out c d # backslash-newline is a continuation
|
|
89
|
+
continue
|
|
90
|
+
}
|
|
91
|
+
if (c == "\"" || c == "\047") { q = c; out = out c; continue }
|
|
92
|
+
if (c == ";" || c == "|" || c == "&" || c == "\n") { out = out "\n"; continue }
|
|
93
|
+
out = out c
|
|
94
|
+
}
|
|
95
|
+
print out
|
|
96
|
+
}'
|
|
97
|
+
}
|
|
98
|
+
|
|
99
|
+
# Segments matching the extended regex $1, whitespace-normalized, one per line.
|
|
100
|
+
segments_matching() {
|
|
101
|
+
command_segments | tr -s ' \t' ' ' | grep -E -- "$1"
|
|
102
|
+
}
|
|
103
|
+
|
|
104
|
+
# Argument tokens following EACH `git push` in segment $1, one per line.
|
|
105
|
+
# Quotes, backticks, parentheses, and separators are stripped from tokens so
|
|
106
|
+
# `$(git push origin main)` and `bash -c "git push origin main"` still yield
|
|
107
|
+
# `main`. Every occurrence in the segment is read, not just the last one.
|
|
108
|
+
push_tokens() {
|
|
109
|
+
printf '%s\n' "$1" | awk '{ n = split($0, parts, /git[ \t]+push/); for (i = 2; i <= n; i++) print parts[i] }' \
|
|
110
|
+
| tr -s ' \t' '\n\n' | tr -d "\"'\`();|&" | sed 's/[<>].*//' | grep -v '^$'
|
|
111
|
+
}
|
|
112
|
+
|
|
113
|
+
# A command word counts when it appears at a segment's start, after
|
|
114
|
+
# whitespace, after an opening quote, backtick, or parenthesis, or after a
|
|
115
|
+
# path (`/usr/bin/git`).
|
|
116
|
+
_cmd_prefix="(^|[[:space:](\`\"'/])"
|
|
117
|
+
_push_segment_re="${_cmd_prefix}git +push([[:space:]]|$)"
|
|
118
|
+
|
|
119
|
+
# Does any `git push` destination in the command equal branch $1? Reads each
|
|
120
|
+
# push segment's own tokens only; checks bare tokens and the right-hand side
|
|
121
|
+
# of `src:dst` refspecs, stripping a leading `+` and a `refs/heads/` prefix.
|
|
122
|
+
push_targets_ref() {
|
|
123
|
+
local target="$1" seg tok dst
|
|
124
|
+
while IFS= read -r seg; do
|
|
125
|
+
while IFS= read -r tok; do
|
|
126
|
+
case "$tok" in
|
|
127
|
+
-*) continue ;;
|
|
128
|
+
esac
|
|
129
|
+
tok="${tok#+}"
|
|
130
|
+
dst="${tok##*:}"
|
|
131
|
+
tok="${tok#refs/heads/}"
|
|
132
|
+
dst="${dst#refs/heads/}"
|
|
133
|
+
if [ "$tok" = "$target" ] || [ "$dst" = "$target" ]; then
|
|
134
|
+
return 0
|
|
135
|
+
fi
|
|
136
|
+
done < <(push_tokens "$seg")
|
|
137
|
+
done < <(segments_matching "$_push_segment_re")
|
|
138
|
+
return 1
|
|
139
|
+
}
|
|
140
|
+
|
|
57
141
|
# --- Rule 1: never merge/push into main ---------------------------------------
|
|
58
|
-
# Block
|
|
59
|
-
#
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
142
|
+
# Block a push whose destination is main, and any merge/PR-merge that targets
|
|
143
|
+
# main. Branch-creation and normal feature pushes are unaffected, including a
|
|
144
|
+
# feature push chained with `gh pr create --base main` (issue #256).
|
|
145
|
+
if push_targets_ref main; then
|
|
146
|
+
block "pushing to 'main' is not allowed. Open a PR; only the user may merge into main."
|
|
147
|
+
fi
|
|
64
148
|
|
|
65
149
|
# `git merge` while the checked-out branch is main (i.e. merging INTO main).
|
|
66
150
|
if printf '%s' "$norm" | grep -Eq '(^|[;&|[:space:]])git +merge([[:space:]]|$)'; then
|
|
@@ -71,17 +155,19 @@ if printf '%s' "$norm" | grep -Eq '(^|[;&|[:space:]])git +merge([[:space:]]|$)';
|
|
|
71
155
|
fi
|
|
72
156
|
|
|
73
157
|
# `gh pr merge` targeting main (either via --base main or merging a PR onto main).
|
|
74
|
-
|
|
75
|
-
|
|
158
|
+
# Checked per segment, so a later `gh pr create --base main` in the same
|
|
159
|
+
# command is not read as this merge's base (issue #256).
|
|
160
|
+
while IFS= read -r _seg; do
|
|
161
|
+
if printf '%s' "$_seg" | grep -Eq -- "(--base|-B)[ =][\"']?main([^[:alnum:]_./-]|$)"; then
|
|
76
162
|
block "merging a PR into 'main' is not allowed. Only the user may merge into main."
|
|
77
163
|
fi
|
|
78
164
|
# No explicit base given: gh defaults to the PR's base. Warn-block to be safe
|
|
79
165
|
# for the common case where PRs target main. Story PRs targeting integration
|
|
80
166
|
# branches should pass --base <integration-branch> explicitly.
|
|
81
|
-
if ! printf '%s' "$
|
|
167
|
+
if ! printf '%s' "$_seg" | grep -Eq -- '--base[ =]|-B[ =]'; then
|
|
82
168
|
block "refusing 'gh pr merge' without an explicit --base. PRs to main require user approval; for integration branches pass --base <integration-branch>."
|
|
83
169
|
fi
|
|
84
|
-
|
|
170
|
+
done < <(segments_matching 'gh +pr +merge')
|
|
85
171
|
|
|
86
172
|
# --- Rule 2: Conventional Commits for git commit ------------------------------
|
|
87
173
|
# Inspect inline -m / --message messages. Commits via editor or -F file are not
|
|
@@ -257,10 +257,10 @@ memo-cli 1.3.0 adds a second axis of scoping — **banks** — and a third field
|
|
|
257
257
|
|
|
258
258
|
A bank is a namespace for entries, resolved in this priority order (B3): `--bank <id>` flag > `$MEMO_BANK` env var > `config.bank.default` > `kb`. `kb` is the shared, org-wide knowledge base every repo reads from by default; any other bank id (kebab-case or UUID) is a **private** bank — conventionally named `<agent-name>-memory` (e.g. `developer-memory`, `technical-writer-memory`, `product-engineer-memory`, `planner-memory`) for a long-lived agent's own session memory.
|
|
259
259
|
|
|
260
|
-
|
|
260
|
+
**Agents: always pass `--bank <id>` literally on every command.** Agent runtimes run each shell command in a fresh shell, so an `export MEMO_BANK=…` from an earlier command is gone by the next one. An unquoted empty `$MEMO_BANK` is dropped by the shell, and the flag parser then reads the next token as the bank id (`--bank --rationale …` → bank `--rationale`), which memo-cli rejects with `VALIDATION_FAILED` (dev-tasks issue #253). Never write `--bank $MEMO_BANK` in an agent prompt or command.
|
|
261
261
|
|
|
262
262
|
```bash
|
|
263
|
-
|
|
263
|
+
memo write --bank developer-memory ... # bank id convention: <agent-name>-memory
|
|
264
264
|
```
|
|
265
265
|
|
|
266
266
|
`kb` and private banks are isolated from each other: a `search`/`list`/`recall` scoped to a private bank never returns `kb` entries and vice versa, unless you explicitly pass `--bank kb`.
|
|
@@ -275,7 +275,7 @@ export MEMO_BANK=developer-memory
|
|
|
275
275
|
|
|
276
276
|
`--kind` is case-insensitive (`--kind Self`, `--kind SELF`, `--kind self` all normalize to `self`). Default kind is `episodic` in a private bank, `semantic` in `kb`.
|
|
277
277
|
|
|
278
|
-
**Rule of thumb for agent definitions in this repository:** intent/outcome entries are `--kind episodic --session ISSUE-<n> --bank
|
|
278
|
+
**Rule of thumb for agent definitions in this repository:** intent/outcome entries are `--kind episodic --session ISSUE-<n> --bank <agent>-memory`; ADR/decision entries stay `--kind semantic --bank kb`.
|
|
279
279
|
|
|
280
280
|
---
|
|
281
281
|
|
|
@@ -298,7 +298,7 @@ Episodic example — intent entry in a private bank:
|
|
|
298
298
|
memo write \
|
|
299
299
|
--kind episodic \
|
|
300
300
|
--session ISSUE-42 \
|
|
301
|
-
--bank
|
|
301
|
+
--bank <agent>-memory \
|
|
302
302
|
--rationale "Context: Starting ISSUE-42. Decision: implement via a middleware. Impact: affects the auth pipeline." \
|
|
303
303
|
--tags "auth,issue-42,intent,middleware" \
|
|
304
304
|
--entry-type decision \
|
|
@@ -391,7 +391,7 @@ Most-recent-first listing with optional date range.
|
|
|
391
391
|
### `memo timeline` — Replay Episodic Memory
|
|
392
392
|
|
|
393
393
|
```bash
|
|
394
|
-
memo timeline --bank
|
|
394
|
+
memo timeline --bank <agent>-memory --session ISSUE-42 --json
|
|
395
395
|
```
|
|
396
396
|
|
|
397
397
|
Replays episodic memory **in sequence order** — never ranked. Two shapes:
|
|
@@ -479,7 +479,7 @@ Migrates legacy v1 stored payloads to schema v2, idempotently (a point that alre
|
|
|
479
479
|
### `memo recall` — One-Call Context Restore
|
|
480
480
|
|
|
481
481
|
```bash
|
|
482
|
-
memo recall "<task description>" --bank
|
|
482
|
+
memo recall "<task description>" --bank <agent>-memory --json
|
|
483
483
|
```
|
|
484
484
|
|
|
485
485
|
The 1.3.0 replacement for the four-command session-start sequence (`list` + `tags list` + `search` + `search --scope related`). Gathers, in one call (≤ 4 s target):
|
|
@@ -504,7 +504,7 @@ When the budget is tight, sections are trimmed in this order: `conflicts` → `l
|
|
|
504
504
|
|
|
505
505
|
**On failure:** `memo recall` exits `2` on an embeddings failure (`EMBEDDING_API_ERROR`) or a mid-gather Qdrant failure (`QDRANT_OPERATION_FAILED`) — there is no partial-bundle fallback. Treat this the same as any other exit-`2` failure: surface the warning, and continue the session without recalled context rather than blocking on it.
|
|
506
506
|
|
|
507
|
-
**When
|
|
507
|
+
**When no private bank is passed** (resolves to `kb`): `SELF`, `MINE`, and `LAST SESSION` are omitted from the response entirely (omitted keys, not empty arrays) — you still get `POLICIES`, `SHARED`, `CONFLICTS`.
|
|
508
508
|
|
|
509
509
|
**Fallback when `memo recall` is unavailable** (`memo --version` below `1.3.0`, or the command errors as unrecognized): fall back to the four-command sequence documented under **Session Start — Restore Context** in `SKILL.md`.
|
|
510
510
|
|
|
@@ -571,7 +571,7 @@ Exactly one of `--id`, `--all-by-repo`, or `--all-by-org` is required.
|
|
|
571
571
|
memo setup validate
|
|
572
572
|
|
|
573
573
|
# 2. Restore SELF, POLICIES, SHARED, MINE, LAST SESSION, CONFLICTS in one bundle
|
|
574
|
-
memo recall "<current task or feature description>" --bank
|
|
574
|
+
memo recall "<current task or feature description>" --bank <agent>-memory --json
|
|
575
575
|
```
|
|
576
576
|
|
|
577
577
|
**Fallback (`memo --version` below `1.3.0`):** run this sequence instead, before writing a single line of code:
|
|
@@ -968,12 +968,12 @@ memo setup init --repo <r> --org <o> --domain <d> # Initialize conf
|
|
|
968
968
|
memo setup validate # Verify config
|
|
969
969
|
memo setup show [--json] # Display config
|
|
970
970
|
|
|
971
|
-
memo recall "<task>" --bank
|
|
971
|
+
memo recall "<task>" --bank <agent>-memory [--json] # Restore full context (1.3.0+)
|
|
972
972
|
memo write --rationale "..." --tags "a,b,c" [--json] # Record a semantic decision (kb)
|
|
973
|
-
memo write --kind episodic --session ID --bank
|
|
973
|
+
memo write --kind episodic --session ID --bank <agent>-memory [--json] # Record an intent/outcome entry
|
|
974
974
|
memo search "query" [--scope related] [--bank ID] [--kind K] [--json] # Semantic search
|
|
975
975
|
memo list [--from DATE] [--to DATE] [--bank ID] [--kind K] [--json] # Browse entries
|
|
976
|
-
memo timeline [--session ID] --bank
|
|
976
|
+
memo timeline [--session ID] --bank <agent>-memory [--last N] [--json] # Replay episodic memory in order
|
|
977
977
|
memo tags list [--sort frequency] [--json] # Discover tags
|
|
978
978
|
memo inspect [--json] # Global facets
|
|
979
979
|
memo bank list [--json] # List all banks
|
|
@@ -21,10 +21,12 @@ If validation fails, run: `memo setup init --repo <repo> --org <org> --domain <d
|
|
|
21
21
|
|
|
22
22
|
## Banks and Kinds (memo-cli 1.3.0+)
|
|
23
23
|
|
|
24
|
-
A **bank** is a namespace an agent's entries live in — the shared `kb` (default, semantic knowledge base) or a private bank like `developer-memory`, one per long-lived agent. Set `--bank <id>` on any command
|
|
24
|
+
A **bank** is a namespace an agent's entries live in — the shared `kb` (default, semantic knowledge base) or a private bank like `developer-memory`, one per long-lived agent. Set `--bank <id>` on any command.
|
|
25
|
+
|
|
26
|
+
**Agents: always pass `--bank <id>` literally on every command.** Agent runtimes run each shell command in a fresh shell, so an `export MEMO_BANK=…` from an earlier command is gone by the next one. An unquoted empty `$MEMO_BANK` is dropped by the shell, and the flag parser then reads the next token as the bank id (`--bank --rationale …` → bank `--rationale`), which memo-cli rejects with `VALIDATION_FAILED` (dev-tasks issue #253). Never write `--bank $MEMO_BANK` in an agent prompt or command.
|
|
25
27
|
|
|
26
28
|
```bash
|
|
27
|
-
|
|
29
|
+
memo write --bank developer-memory ... # bank id convention: <agent-name>-memory
|
|
28
30
|
```
|
|
29
31
|
|
|
30
32
|
Every entry has a **kind**:
|
|
@@ -44,10 +46,10 @@ Rule of thumb: episodic entries are per-session chatter that lives in your priva
|
|
|
44
46
|
**memo-cli 1.3.0+:** one call restores the full context bundle (SELF, POLICIES, SHARED, MINE, LAST SESSION, CONFLICTS):
|
|
45
47
|
|
|
46
48
|
```bash
|
|
47
|
-
memo recall "<current task description>" --bank
|
|
49
|
+
memo recall "<current task description>" --bank <agent>-memory --json
|
|
48
50
|
```
|
|
49
51
|
|
|
50
|
-
If
|
|
52
|
+
If no bank is passed (and `MEMO_BANK` is unset), `recall` resolves to `kb` and omits the private-only sections (`SELF`, `MINE`, `LAST SESSION`).
|
|
51
53
|
|
|
52
54
|
**Fallback (`memo --version` < 1.3.0, or `memo recall` unavailable):** run the four-command sequence instead:
|
|
53
55
|
|
|
@@ -75,7 +77,7 @@ Synthesize findings (either path) into:
|
|
|
75
77
|
memo write \
|
|
76
78
|
--kind episodic \
|
|
77
79
|
--session ISSUE-<number> \
|
|
78
|
-
--bank
|
|
80
|
+
--bank <agent>-memory \
|
|
79
81
|
--rationale "Context: Starting ISSUE-<##> because <trigger>. Decision: implement via <approach>, preserving <constraints>. Impact: affects <modules/contracts>." \
|
|
80
82
|
--tags "<domain>,issue-<number>,intent,<impact-tag>" \
|
|
81
83
|
--entry-type decision \
|
|
@@ -91,7 +93,7 @@ memo write \
|
|
|
91
93
|
memo write \
|
|
92
94
|
--kind episodic \
|
|
93
95
|
--session ISSUE-<number> \
|
|
94
|
-
--bank
|
|
96
|
+
--bank <agent>-memory \
|
|
95
97
|
--rationale "Context: Completed ISSUE-<##>. Delivery: shipped <behavior>, deviations <none|details>, AC <x/y> verified. Impact: quality gates test=<p/f>; lint=<p/f>; format:check=<p/f>; typecheck=<p/f>; audit=<p/f>." \
|
|
96
98
|
--tags "<domain>,issue-<number>,outcome,gates-pass" \
|
|
97
99
|
--entry-type decision \
|
|
@@ -180,12 +182,12 @@ No memo action in Phase 2. `memo used` and `memo decay` arrive with memo-cli 1.4
|
|
|
180
182
|
|
|
181
183
|
```
|
|
182
184
|
memo setup validate # Verify config
|
|
183
|
-
memo recall "<task>" --bank
|
|
185
|
+
memo recall "<task>" --bank <agent>-memory --json # Restore full context (1.3.0+)
|
|
184
186
|
memo write --rationale "..." --tags "a,b,c" --json # Record a semantic decision (kb)
|
|
185
|
-
memo write --kind episodic --session ID --bank
|
|
187
|
+
memo write --kind episodic --session ID --bank <agent>-memory # Record an intent/outcome entry
|
|
186
188
|
memo search "query" [--scope related] --json # Semantic search
|
|
187
189
|
memo list [--limit N] --json # Browse recent
|
|
188
|
-
memo timeline [--session ID] --bank
|
|
190
|
+
memo timeline [--session ID] --bank <agent>-memory --json # Replay episodic memory in order
|
|
189
191
|
memo tags list [--sort frequency] --json # Discover tags
|
|
190
192
|
memo inspect --json # Global facets
|
|
191
193
|
memo bank list --json # List all banks
|
|
@@ -82,6 +82,7 @@ fix(web): stop double-submitting the checkout form
|
|
|
82
82
|
- PR title **MUST** follow Conventional Commits (e.g., `feat: implement issue 37`).
|
|
83
83
|
- PR description **MUST** include `Closes #<issue-number>`.
|
|
84
84
|
5. You **MUST** ensure the task list in the GitHub Issue matches the local `/workstream/tasks-*.md` file.
|
|
85
|
+
6. **memo intent (when memo-cli is available):** Before the first implementation sub-task, you **MUST** run the memo-cli Availability Check and write the episodic intent entry defined in the `developer` agent contract (**memo-cli Integration → Intent Entry**), naming the bank literally (`--bank developer-memory`, never `--bank $MEMO_BANK`). Record `memo_intent` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — a failed write is retried once and then reported, never dropped silently.
|
|
85
86
|
|
|
86
87
|
If `github-ops` delegation is unavailable in the current runtime, you **MUST** apply `github-ops` conventions directly and explicitly note that fallback in your status output.
|
|
87
88
|
|
|
@@ -148,14 +149,17 @@ When `workstream/decisions-<feature>.md` exists and was read per step 2 above:
|
|
|
148
149
|
5. `technical-writer` validation **MUST** include a drift/stale-doc check report, and completion **MUST NOT** proceed while unresolved drift remains.
|
|
149
150
|
6. A `qa-engineer` pass **MUST** have run and `coverage_gate` **MUST** be recorded as `PASS`, `FAIL`, or `SKIPPED(<reason>)`. The reason **MUST** be non-empty when skipped; an omitted field is treated as incomplete. A `FAIL` or `SKIPPED` value does not block completion — only omission does.
|
|
150
151
|
7. A `verifier` audit in `audit` mode **MUST** have run against the delivered implementation, with its human-readable summary posted to the issue/PR. This gate is mandatory and non-skippable — it **MUST NOT** be skipped regardless of drift findings, and drift findings reported by this audit **MUST NOT** block completion. This condition is satisfied once the audit has run and been posted; any resulting drift is handled by `product-engineer`'s `activity-drift-reconciliation` flow after this gate, not before it.
|
|
151
|
-
8.
|
|
152
|
-
9. The PR **MUST** be
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
152
|
+
8. **memo outcome (when memo-cli is available):** Before the PR is converted to ready for review, you **MUST** write the episodic outcome entry defined in the `developer` agent contract (**memo-cli Integration → Outcome Entry**) and record `memo_outcome` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`. A `failed` or `skipped` value does not block completion — only an omitted field does.
|
|
153
|
+
9. The PR **MUST** be converted from draft to ready for review.
|
|
154
|
+
10. The PR **MUST** be approved by the appropriate reviewer per the merge authority policy in `github-ops`:
|
|
155
|
+
|
|
156
|
+
- PRs targeting an **integration branch**: `planner` reviews and approves.
|
|
157
|
+
- PRs targeting **`main`**: the **user** reviews and approves.
|
|
158
|
+
|
|
159
|
+
11. The PR **MUST** be merged by the authorized party (planner for integration branches, user for `main`).
|
|
160
|
+
12. You **MUST NOT** close the GitHub Issue until the PR is approved **AND** merged.
|
|
161
|
+
13. You **MUST NOT** close the issue while the PR is still in draft or pending review.
|
|
162
|
+
14. You **MUST** notify the user when the PR is ready for review — explicitly inform them so they can review and merge.
|
|
159
163
|
|
|
160
164
|
---
|
|
161
165
|
|
package/AGENTS.md
CHANGED
|
@@ -4,10 +4,11 @@ Portable, repo-installed workflow harness for structured, PRD-driven AI-assisted
|
|
|
4
4
|
|
|
5
5
|
## Contracts
|
|
6
6
|
|
|
7
|
-
| File
|
|
8
|
-
|
|
|
9
|
-
| `/DESIGN.md`
|
|
10
|
-
| `/TESTING.md`
|
|
7
|
+
| File | Owner | Purpose |
|
|
8
|
+
| ----------------- | ------------------ | ---------------------------------------------- |
|
|
9
|
+
| `/DESIGN.md` | `ux-engineer` | Canonical design-system tokens and UI guidance |
|
|
10
|
+
| `/TESTING.md` | `qa-engineer` | Layer taxonomy, runners, thresholds, fixtures |
|
|
11
|
+
| `docs/roadmap.md` | `product-engineer` | PRD phases/waves: done, in progress, missing |
|
|
11
12
|
|
|
12
13
|
If `/DESIGN.md` is missing and scope includes UI work, agents **MUST** create a baseline before finalizing design-dependent outputs. An unfilled `/TESTING.md` placeholder means "no standard established", never permission.
|
|
13
14
|
|
|
@@ -113,7 +114,8 @@ All agents **MUST**:
|
|
|
113
114
|
- Run `qa-engineer` at completion gate (record `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`)
|
|
114
115
|
- Run `verifier` audit (mandatory, non-skippable) before PR is ready; drift findings route to `product-engineer`
|
|
115
116
|
- Follow test-first design: write tests before implementation code
|
|
116
|
-
- If `memo-cli` is available: read/write entries per role
|
|
117
|
+
- If `memo-cli` is available: read/write entries per role, naming `--bank <id>` literally on every command (never `--bank $MEMO_BANK`), and report every write as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — never drop a failure silently
|
|
118
|
+
- Keep `docs/roadmap.md` current: `product-engineer` reads it at session start and adds a row per PRD phase/wave; `planner` reads it in Phase 0 and updates the delivered rows in the consolidated PR; `verifier` reports a mismatch with merged work as an advisory finding
|
|
117
119
|
- **Foundation documents: resolve the new name, fall back to the old one.** The canonical names are `docs/product.md` and `docs/tech.md`. A repository installed before the rename still carries `docs/product-context.md` and `docs/technical-guidelines.md`, and `dev-tasks update` never renames a consumer-owned file on its own. So when **reading** a foundation document, resolve the new name first and fall back to the old one only when the new name is absent; when **writing**, always write the new name. Propose `dev-tasks migrate docs` on encountering an old name. This applies to every agent and skill that reads these documents, for one release cycle (FR-45)
|
|
118
120
|
- Deliver a runbook in the **same PR** as any new or materially changed script under `templates/scripts/`, workflow under `templates/workflows/` or `.github/workflows/`, or `infra-engineer` change kind (FR-49a). Updating an existing runbook satisfies this
|
|
119
121
|
- Route a docs-structure failure in `validate` to `technical-writer`, never to `housekeeping` (FR-51): `technical-writer` owns documentation structure and content
|
package/AGENTS.md.template
CHANGED
|
@@ -8,6 +8,7 @@ Portable, repo-installed workflow harness for structured, PRD-driven AI-assisted
|
|
|
8
8
|
| ------------- | ------------- | ---------------------------------------------- |
|
|
9
9
|
| `/DESIGN.md` | `ux-engineer` | Canonical design-system tokens and UI guidance |
|
|
10
10
|
| `/TESTING.md` | `qa-engineer` | Layer taxonomy, runners, thresholds, fixtures |
|
|
11
|
+
| `docs/roadmap.md` | `product-engineer` | PRD phases/waves: done, in progress, missing |
|
|
11
12
|
|
|
12
13
|
If `/DESIGN.md` is missing and scope includes UI work, agents **MUST** create a baseline before finalizing design-dependent outputs. An unfilled `/TESTING.md` placeholder means "no standard established", never permission.
|
|
13
14
|
|
|
@@ -113,7 +114,8 @@ All agents **MUST**:
|
|
|
113
114
|
- Run `qa-engineer` at completion gate (record `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`)
|
|
114
115
|
- Run `verifier` audit (mandatory, non-skippable) before PR is ready; drift findings route to `product-engineer`
|
|
115
116
|
- Follow test-first design: write tests before implementation code
|
|
116
|
-
- If `memo-cli` is available: read/write entries per role
|
|
117
|
+
- If `memo-cli` is available: read/write entries per role, naming `--bank <id>` literally on every command (never `--bank $MEMO_BANK`), and report every write as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)` — never drop a failure silently
|
|
118
|
+
- Keep `docs/roadmap.md` current: `product-engineer` reads it at session start and adds a row per PRD phase/wave; `planner` reads it in Phase 0 and updates the delivered rows in the consolidated PR; `verifier` reports a mismatch with merged work as an advisory finding
|
|
117
119
|
- **Foundation documents: resolve the new name, fall back to the old one.** The canonical names are `docs/product.md` and `docs/tech.md`. A repository installed before the rename still carries `docs/product-context.md` and `docs/technical-guidelines.md`, and `dev-tasks update` never renames a consumer-owned file on its own. So when **reading** a foundation document, resolve the new name first and fall back to the old one only when the new name is absent; when **writing**, always write the new name. Propose `dev-tasks migrate docs` on encountering an old name. This applies to every agent and skill that reads these documents, for one release cycle (FR-45)
|
|
118
120
|
- Deliver a runbook in the **same PR** as any new or materially changed script under `templates/scripts/`, workflow under `templates/workflows/` or `.github/workflows/`, or `infra-engineer` change kind (FR-49a). Updating an existing runbook satisfies this
|
|
119
121
|
- Route a docs-structure failure in `validate` to `technical-writer`, never to `housekeeping` (FR-51): `technical-writer` owns documentation structure and content
|
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,25 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/).
|
|
7
7
|
|
|
8
|
+
## [0.16.2] - 2026-10-02
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
|
|
12
|
+
- fix(git-guard): read each command's arguments from its own segment (#257)
|
|
13
|
+
- fix(memo): make memo writes succeed and add docs/roadmap.md (#255)
|
|
14
|
+
|
|
15
|
+
## [Unreleased]
|
|
16
|
+
|
|
17
|
+
### Added
|
|
18
|
+
|
|
19
|
+
- feat(roadmap): `docs/roadmap.md` overview of PRD phases and waves, owned by `product-engineer`, updated by `planner` in the consolidated PR, and checked by a `verifier` roadmap-mismatch finding (#254)
|
|
20
|
+
- feat(memo): `product-engineer` writes confirmed grilling decisions to `kb`; `planner` verifies per-story memo fields and writes one run-outcome entry (#253)
|
|
21
|
+
|
|
22
|
+
### Fixed
|
|
23
|
+
|
|
24
|
+
- fix(git-guard): read each command's arguments from its own segment of a chained command, so a feature push followed by `gh pr create --base main` or a commit message mentioning tags no longer blocks, and every push, merge, and tag command in a chain is checked instead of only the last one (#256)
|
|
25
|
+
- fix(memo): name memo banks literally instead of `--bank $MEMO_BANK`, which is empty in a fresh shell and made every write fail; use `--manual` for `technical-writer` `kb` entries without provenance; record every write result in the closeout payload and gate merges on its presence (#253)
|
|
26
|
+
|
|
8
27
|
## [0.16.1] - 2026-09-23
|
|
9
28
|
|
|
10
29
|
### Fixed
|
package/CLAUDE.md
CHANGED
|
@@ -20,6 +20,7 @@ All work in this repository **MUST**:
|
|
|
20
20
|
- Use canonical `package.json` script names for JS/TS projects: `lint`, `lint:fix`, `format`, `format:check`, `typecheck`, `test`, `test:unit`, `test:integration`, `test:e2e`, `audit`, `validate`.
|
|
21
21
|
- Before developer/planner completion, enforce and record quality gates: `test`, `lint`, `format:check`, `typecheck`, `audit`.
|
|
22
22
|
- `qa-engineer` runs at the completion gate, before the `verifier` audit, and records `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`. Skipping requires a non-empty reason; omitting the field is treated as incomplete.
|
|
23
|
+
- `docs/roadmap.md` is the roadmap overview — one row per PRD phase or wave with status (`Not started` / `In progress` / `Done`), issues/PRs, and what is missing. `product-engineer` reads it at session start and owns its rows; `planner` reads it in Phase 0 and updates the rows a run delivers in the consolidated PR; the `verifier` reports a roadmap mismatch with merged work as an advisory finding.
|
|
23
24
|
- `/TESTING.md` is the canonical testing contract — owned by `qa-engineer`, kept current by `developer`, and treated as "no standard established" while unfilled.
|
|
24
25
|
- Reference GitHub Issues in branch names and commits; follow the `github-ops` conventions for all GitHub artifacts (issues, PRs, branches, labels, milestones, comments).
|
|
25
26
|
- Treat `/DESIGN.md` as the source of truth for visual tokens, components, and design guidance; update it whenever UI contracts change.
|
|
@@ -40,7 +41,7 @@ GitHub operations run through the **`gh` CLI** (over Bash). The `github-ops` sub
|
|
|
40
41
|
|
|
41
42
|
## memo-cli (Optional)
|
|
42
43
|
|
|
43
|
-
If `memo-cli` is installed and `memo setup validate` passes: `product-engineer` reads context at session start
|
|
44
|
+
If `memo-cli` is installed and `memo setup validate` passes: `product-engineer` reads context at session start and writes each confirmed grilling decision to `kb`; `developer` writes intent/outcome entries per story; `technical-writer` writes one entry per ADR and significant doc change; `planner` verifies per-story memo fields and writes one run-outcome entry. Every memo command names `--bank <id>` literally — never `--bank $MEMO_BANK`, which is empty in a fresh shell and makes memo-cli reject the write. Every write is reported as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`; a failure is never dropped silently. If installed but not configured, ask the user to run `memo setup init` first. If not installed and `memo.config.json` is absent, skip; if `memo.config.json` exists but the binary is missing, warn. See the `memo-cli-usage` skill.
|
|
44
45
|
|
|
45
46
|
---
|
|
46
47
|
|
package/CLAUDE.md.template
CHANGED
|
@@ -20,6 +20,7 @@ All work in this repository **MUST**:
|
|
|
20
20
|
- Use canonical `package.json` script names for JS/TS projects: `lint`, `lint:fix`, `format`, `format:check`, `typecheck`, `test`, `test:unit`, `test:integration`, `test:e2e`, `audit`, `validate`.
|
|
21
21
|
- Before developer/planner completion, enforce and record quality gates: `test`, `lint`, `format:check`, `typecheck`, `audit`.
|
|
22
22
|
- `qa-engineer` runs at the completion gate, before the `verifier` audit, and records `coverage_gate: PASS | FAIL | SKIPPED(<reason>)`. Skipping requires a non-empty reason; omitting the field is treated as incomplete.
|
|
23
|
+
- `docs/roadmap.md` is the roadmap overview — one row per PRD phase or wave with status (`Not started` / `In progress` / `Done`), issues/PRs, and what is missing. `product-engineer` reads it at session start and owns its rows; `planner` reads it in Phase 0 and updates the rows a run delivers in the consolidated PR; the `verifier` reports a roadmap mismatch with merged work as an advisory finding.
|
|
23
24
|
- `/TESTING.md` is the canonical testing contract — owned by `qa-engineer`, kept current by `developer`, and treated as "no standard established" while unfilled.
|
|
24
25
|
- Reference GitHub Issues in branch names and commits; follow the `github-ops` conventions for all GitHub artifacts (issues, PRs, branches, labels, milestones, comments).
|
|
25
26
|
- Treat `/DESIGN.md` as the source of truth for visual tokens, components, and design guidance; update it whenever UI contracts change.
|
|
@@ -40,7 +41,7 @@ GitHub operations run through the **`gh` CLI** (over Bash). The `github-ops` sub
|
|
|
40
41
|
|
|
41
42
|
## memo-cli (Optional)
|
|
42
43
|
|
|
43
|
-
If `memo-cli` is installed and `memo setup validate` passes: `product-engineer` reads context at session start
|
|
44
|
+
If `memo-cli` is installed and `memo setup validate` passes: `product-engineer` reads context at session start and writes each confirmed grilling decision to `kb`; `developer` writes intent/outcome entries per story; `technical-writer` writes one entry per ADR and significant doc change; `planner` verifies per-story memo fields and writes one run-outcome entry. Every memo command names `--bank <id>` literally — never `--bank $MEMO_BANK`, which is empty in a fresh shell and makes memo-cli reject the write. Every write is reported as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`; a failure is never dropped silently. If installed but not configured, ask the user to run `memo setup init` first. If not installed and `memo.config.json` is absent, skip; if `memo.config.json` exists but the binary is missing, warn. See the `memo-cli-usage` skill.
|
|
44
45
|
|
|
45
46
|
---
|
|
46
47
|
|