@llipe.com/dev-tasks 0.16.2 → 0.17.0
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 +8 -3
- package/.claude/agents/github-ops.md +187 -59
- package/.claude/agents/technical-writer.md +1 -1
- package/.claude/agents/verifier.md +10 -5
- package/.claude/commands/planner.md +110 -15
- package/.claude/commands/product-engineer.md +27 -3
- package/.claude/hooks/git-guard.sh +2 -2
- package/.claude/skills/activity-init/SKILL.md +4 -0
- package/.claude/skills/activity-publish-github/SKILL.md +84 -15
- package/.claude/skills/git-ops/SKILL.md +6 -6
- package/.claude/skills/implement/SKILL.md +29 -13
- package/.claude/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.claude/skills/memo-cli-usage/SKILL.md +3 -1
- package/.claude/skills/plan/SKILL.md +6 -0
- package/.github/agents/developer.agent.md +8 -3
- package/.github/agents/github-ops.agent.md +182 -64
- package/.github/agents/planner.agent.md +123 -28
- package/.github/agents/product-engineer.agent.md +27 -3
- package/.github/agents/technical-writer.agent.md +1 -1
- package/.github/agents/verifier.agent.md +10 -5
- package/.github/instructions/implement.instructions.md +29 -13
- package/.github/instructions/plan.instructions.md +6 -0
- package/.github/skills/activity-init/SKILL.md +4 -0
- package/.github/skills/activity-publish-github/SKILL.md +84 -15
- package/.github/skills/git-ops/SKILL.md +6 -6
- package/.github/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.github/skills/memo-cli-usage/SKILL.md +3 -1
- package/.kiro/agents/developer.md +8 -3
- package/.kiro/agents/github-ops.md +182 -64
- package/.kiro/agents/planner.md +123 -28
- package/.kiro/agents/product-engineer.md +27 -3
- package/.kiro/agents/technical-writer.md +1 -1
- package/.kiro/agents/verifier.md +10 -5
- package/.kiro/skills/activity-init/SKILL.md +4 -0
- package/.kiro/skills/activity-publish-github/SKILL.md +84 -15
- package/.kiro/skills/git-ops/SKILL.md +6 -6
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +1 -0
- package/.kiro/skills/memo-cli-usage/SKILL.md +3 -1
- package/.kiro/steering/implement.md +29 -13
- package/.kiro/steering/plan.md +6 -0
- package/CHANGELOG.md +42 -0
- package/README.md +79 -7
- package/TESTING.md +108 -30
- package/dist/bin/dev-tasks.d.ts +1 -1
- package/dist/bin/dev-tasks.js +126 -4
- package/dist/bin/dev-tasks.js.map +1 -1
- package/dist/bin/parse-args.d.ts +49 -1
- package/dist/bin/parse-args.d.ts.map +1 -1
- package/dist/bin/parse-args.js +132 -11
- package/dist/bin/parse-args.js.map +1 -1
- package/dist/core/checks/decision-log-format.d.ts +24 -3
- package/dist/core/checks/decision-log-format.d.ts.map +1 -1
- package/dist/core/checks/decision-log-format.js +43 -3
- package/dist/core/checks/decision-log-format.js.map +1 -1
- package/dist/core/checks/index.d.ts +2 -0
- package/dist/core/checks/index.d.ts.map +1 -1
- package/dist/core/checks/index.js +1 -0
- package/dist/core/checks/index.js.map +1 -1
- package/dist/core/checks/roadmap.d.ts +40 -0
- package/dist/core/checks/roadmap.d.ts.map +1 -0
- package/dist/core/checks/roadmap.js +78 -0
- package/dist/core/checks/roadmap.js.map +1 -0
- package/dist/core/migrate-projects/answers.d.ts +63 -0
- package/dist/core/migrate-projects/answers.d.ts.map +1 -0
- package/dist/core/migrate-projects/answers.js +79 -0
- package/dist/core/migrate-projects/answers.js.map +1 -0
- package/dist/core/migrate-projects/apply.d.ts +51 -0
- package/dist/core/migrate-projects/apply.d.ts.map +1 -0
- package/dist/core/migrate-projects/apply.js +828 -0
- package/dist/core/migrate-projects/apply.js.map +1 -0
- package/dist/core/migrate-projects/classify.d.ts +93 -0
- package/dist/core/migrate-projects/classify.d.ts.map +1 -0
- package/dist/core/migrate-projects/classify.js +170 -0
- package/dist/core/migrate-projects/classify.js.map +1 -0
- package/dist/core/migrate-projects/conventions.d.ts +118 -0
- package/dist/core/migrate-projects/conventions.d.ts.map +1 -0
- package/dist/core/migrate-projects/conventions.js +213 -0
- package/dist/core/migrate-projects/conventions.js.map +1 -0
- package/dist/core/migrate-projects/gh.d.ts +40 -0
- package/dist/core/migrate-projects/gh.d.ts.map +1 -0
- package/dist/core/migrate-projects/gh.js +115 -0
- package/dist/core/migrate-projects/gh.js.map +1 -0
- package/dist/core/migrate-projects/index.d.ts +61 -0
- package/dist/core/migrate-projects/index.d.ts.map +1 -0
- package/dist/core/migrate-projects/index.js +183 -0
- package/dist/core/migrate-projects/index.js.map +1 -0
- package/dist/core/migrate-projects/local-reader.d.ts +8 -0
- package/dist/core/migrate-projects/local-reader.d.ts.map +1 -0
- package/dist/core/migrate-projects/local-reader.js +30 -0
- package/dist/core/migrate-projects/local-reader.js.map +1 -0
- package/dist/core/migrate-projects/map.d.ts +36 -0
- package/dist/core/migrate-projects/map.d.ts.map +1 -0
- package/dist/core/migrate-projects/map.js +75 -0
- package/dist/core/migrate-projects/map.js.map +1 -0
- package/dist/core/migrate-projects/plan.d.ts +71 -0
- package/dist/core/migrate-projects/plan.d.ts.map +1 -0
- package/dist/core/migrate-projects/plan.js +638 -0
- package/dist/core/migrate-projects/plan.js.map +1 -0
- package/dist/core/migrate-projects/planfile.d.ts +149 -0
- package/dist/core/migrate-projects/planfile.d.ts.map +1 -0
- package/dist/core/migrate-projects/planfile.js +608 -0
- package/dist/core/migrate-projects/planfile.js.map +1 -0
- package/dist/core/migrate-projects/roadmap.d.ts +43 -0
- package/dist/core/migrate-projects/roadmap.d.ts.map +1 -0
- package/dist/core/migrate-projects/roadmap.js +54 -0
- package/dist/core/migrate-projects/roadmap.js.map +1 -0
- package/dist/core/migrate-projects/snapshot.d.ts +91 -0
- package/dist/core/migrate-projects/snapshot.d.ts.map +1 -0
- package/dist/core/migrate-projects/snapshot.js +285 -0
- package/dist/core/migrate-projects/snapshot.js.map +1 -0
- package/dist/core/migrate-projects/summary.d.ts +27 -0
- package/dist/core/migrate-projects/summary.d.ts.map +1 -0
- package/dist/core/migrate-projects/summary.js +35 -0
- package/dist/core/migrate-projects/summary.js.map +1 -0
- package/package.json +8 -6
|
@@ -8,27 +8,36 @@ Publish user stories as GitHub Issues so GitHub becomes the source of truth for
|
|
|
8
8
|
|
|
9
9
|
## Goal
|
|
10
10
|
|
|
11
|
-
Take a list of user stories and publish them as GitHub Issues using
|
|
11
|
+
Take a list of user stories and publish them as GitHub Issues using the `gh` CLI, under one PRD tracking issue and one wave tracking issue, so GitHub becomes the source of truth for execution tracking and a GitHub Project can show the hierarchy and per-wave progress with no extra work.
|
|
12
12
|
|
|
13
13
|
## Context
|
|
14
14
|
|
|
15
|
-
This activity assumes the following
|
|
15
|
+
This activity assumes the following documents exist:
|
|
16
16
|
|
|
17
17
|
- `user-stories-[prd-name].md` — The comprehensive list of user stories (produced by the **generate-stories** activity)
|
|
18
|
+
- `docs/roadmap.md` — The roadmap row for this PRD; its `Phase/Wave` cell is the wave `<id>` used in the wave tracking issue title (github-ops § Title Format)
|
|
18
19
|
|
|
19
20
|
## Process
|
|
20
21
|
|
|
21
22
|
1. **Receive Input:** User provides the reference to the user stories file and the GitHub repository target.
|
|
22
23
|
2. **Clarify Publishing Rules:** You **MUST** ask for labeling, milestones, assignees, and any issue template constraints, and you **MUST** align them with `github-ops` conventions.
|
|
23
|
-
3. **
|
|
24
|
-
|
|
25
|
-
|
|
24
|
+
3. **Find or Create the Tracking Issues:** Before any story is created, you **MUST** find or create the PRD tracking issue, then the wave tracking issue. Each is found by its `level:` label plus its title prefix (the title forms are defined by github-ops § Title Format); nothing is stored in a workstream file.
|
|
25
|
+
- PRD: `gh issue list --label "level: prd" --search "[PRD-<name>] in:title" --state open --json number,title --jq 'map(select(.title | startswith("[PRD-<name>]")))'`
|
|
26
|
+
- Wave: `gh issue list --label "level: wave" --search "[PRD-<name>] Wave <id>: in:title" --state open --json number,title --jq 'map(select(.title | startswith("[PRD-<name>] Wave <id>:")))'`
|
|
27
|
+
- The `--jq` filter is applied client-side before counting, because GitHub's `in:title` search tokenises brackets and hyphens leniently and can return siblings such as `[PRD-<name>-v2]`.
|
|
28
|
+
- Exactly one match: reuse that issue number. Zero matches: create the issue with `gh issue create --title ... --label "level: prd" --body-file <path>` (or `level: wave`); tracking issues carry their `level:` label only, never `type:` or `priority:`. More than one match: stop, list the matching issue numbers, and ask the user which one to keep; never pick one silently.
|
|
29
|
+
- The PRD issue body follows the PRD tracking issue template and the wave issue body the wave tracking issue template, both under Issue Formatting Rules.
|
|
30
|
+
4. **Map Stories to Issues:** You **MUST** create one GitHub Issue per user story, labeled `level: story` plus exactly one `type:` label from the github-ops type set (`enhancement`, `bug`, `security`, `refactor`, `test`, `docs`, `chore`, `tech-debt`) and one `priority:` label. When a story fits several types, the github-ops tie-break order picks it; a story is never published with zero or two `type:` labels, and never with a retired one such as `type: other` (D-85).
|
|
31
|
+
5. **Publish to GitHub:** You **MUST** delegate issue creation and metadata application to `github-ops` whenever possible. After each story issue is created, you **MUST** attach it as a sub-issue of the wave issue (see Sub-issue Hierarchy).
|
|
32
|
+
6. **Attach and Verify the Hierarchy:** After all stories are created, attach the wave under the PRD issue if not already attached, read both `sub_issues` lists back, and record the `hierarchy:` result in the publication report.
|
|
33
|
+
7. **Write the PRD Status Comment:** After the hierarchy is verified, create or edit the PRD issue's status comment in the shape of github-ops § Status comment's PRD table, found by its marker and written with implement § Status Comment's find-by-marker, create and PATCH procedure: the published wave's row reads `published`, with its wave issue number. An existing row for this wave is edited in place, never added a second time, and every other wave's row is kept as it is. The PRD issue is the one step 3 resolved, as the report's `PRD issue` line records it; when there is none, run step 3's `level: prd` search again, and with no PRD issue, skip the write. Record `prd_status: written | failed(<reason>) | skipped(no PRD issue)` in the publication report; a refused write is `failed(<reason>)`, and a failed write never stops the publication.
|
|
34
|
+
8. **Save Output.**
|
|
26
35
|
|
|
27
36
|
Execution method rules:
|
|
28
37
|
|
|
29
|
-
-
|
|
30
|
-
-
|
|
31
|
-
- The selected method (`
|
|
38
|
+
- The `gh` CLI is the primary execution path for every call in this activity.
|
|
39
|
+
- A GitHub MCP server is optional; if one is configured in this session, it **MAY** be used instead.
|
|
40
|
+
- The selected method (`gh-cli` or `github-mcp`) **MUST** be recorded in the publication report.
|
|
32
41
|
|
|
33
42
|
If `github-ops` delegation is unavailable in the current runtime, you **MUST** apply `github-ops` issue, label, milestone, and comment conventions directly and explicitly note that fallback in your status output.
|
|
34
43
|
|
|
@@ -41,14 +50,17 @@ Attribution rules:
|
|
|
41
50
|
- "Which GitHub repository should I publish to? (`owner/repo`)"
|
|
42
51
|
- "Do you want labels, milestones, or assignees added?"
|
|
43
52
|
- "Should I use a specific issue template or format?"
|
|
44
|
-
- "Do you want a parent epic issue or project board association?"
|
|
45
53
|
- "Should I skip stories below a certain priority or size?"
|
|
46
54
|
|
|
55
|
+
The tracking-issue hierarchy is not optional, so no question asks for it.
|
|
56
|
+
|
|
47
57
|
## Issue Formatting Rules
|
|
48
58
|
|
|
49
|
-
|
|
59
|
+
### Story issues
|
|
60
|
+
|
|
61
|
+
Each story GitHub Issue **MUST** be created using:
|
|
50
62
|
|
|
51
|
-
- **Title:** `
|
|
63
|
+
- **Title:** the `PRD story` row of github-ops § Title Format
|
|
52
64
|
- **Body:**
|
|
53
65
|
- User Story (role, goal, benefit)
|
|
54
66
|
- Context
|
|
@@ -66,6 +78,53 @@ Each GitHub Issue **MUST** be created using:
|
|
|
66
78
|
|
|
67
79
|
For JS/TS projects, command examples in issues **MUST** prefer `pnpm` and canonical scripts (`pnpm run <script>`).
|
|
68
80
|
|
|
81
|
+
### PRD tracking issue body
|
|
82
|
+
|
|
83
|
+
The PRD issue body is the entry point to the whole PRD: its title line, a link to the PRD file and to its `docs/roadmap.md` row, and the list of waves. It carries no checkboxes, because progress lives in the issue's status comment (github-ops § Status comment) and in the sub-issue progress GitHub derives from the hierarchy. Each wave line is added, or its issue number filled in, by the publish run that creates that wave's tracking issue.
|
|
84
|
+
|
|
85
|
+
```markdown
|
|
86
|
+
# <PRD title>
|
|
87
|
+
|
|
88
|
+
PRD: [docs/requirements/prd-<prd-name>.md](/docs/requirements/prd-<prd-name>.md)
|
|
89
|
+
Roadmap: [docs/roadmap.md](/docs/roadmap.md)
|
|
90
|
+
|
|
91
|
+
## Waves
|
|
92
|
+
|
|
93
|
+
- Wave <id>: #<wave-issue> — <wave title>
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
### Wave tracking issue body
|
|
97
|
+
|
|
98
|
+
The wave issue body carries the wave's scope and its artifacts; it carries no checkboxes, because progress lives in the issue's status comment (github-ops § Status comment) and in the sub-issue progress GitHub derives from the hierarchy. `Integration branch` stays `TBD` until the planner starts the run; `Task plan` stays `pending` until the task list exists.
|
|
99
|
+
|
|
100
|
+
```markdown
|
|
101
|
+
Scope: <the wave's scope line from the PRD's delivery table>
|
|
102
|
+
Integration branch: TBD
|
|
103
|
+
|
|
104
|
+
## Artifacts
|
|
105
|
+
|
|
106
|
+
- Specification: [workstream/specification-<prd-name>.md](/workstream/specification-<prd-name>.md)
|
|
107
|
+
- Stories: [workstream/user-stories-<prd-name>.md](/workstream/user-stories-<prd-name>.md)
|
|
108
|
+
- Task plan: pending
|
|
109
|
+
|
|
110
|
+
## Stories
|
|
111
|
+
|
|
112
|
+
- S-001: <title>
|
|
113
|
+
- S-002: <title>
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
### Sub-issue hierarchy
|
|
117
|
+
|
|
118
|
+
Stories are sub-issues of the wave issue, and the wave issue is a sub-issue of the PRD issue. Every call is REST through `gh api` with `repo` scope:
|
|
119
|
+
|
|
120
|
+
- Child numeric id: `gh api repos/{o}/{r}/issues/{n} --jq .id` (the sub-issue endpoint takes the numeric id, not the issue number).
|
|
121
|
+
- Attach a story under the wave, immediately after the story is created: `gh api -X POST repos/{o}/{r}/issues/{wave}/sub_issues -F sub_issue_id=<id>`.
|
|
122
|
+
- Attach the wave under the PRD with the same call against `issues/{prd}/sub_issues`, if not already listed there.
|
|
123
|
+
- Verify: `gh api repos/{o}/{r}/issues/{wave}/sub_issues --jq '.[].number'` lists every story created in this run, and the PRD's list contains the wave.
|
|
124
|
+
- Report `hierarchy: verified(<n> of <n>)` when every attach is confirmed, or `hierarchy: failed(<reason>)` naming the first failed attach. A failed attach is reported, never retried silently, and never stops the remaining stories from being created.
|
|
125
|
+
|
|
126
|
+
Every issue body goes through `--body-file <path>`; inline `--body` is blocked by git-guard.
|
|
127
|
+
|
|
69
128
|
All issue formatting and metadata **MUST** conform to `github-ops` conventions.
|
|
70
129
|
|
|
71
130
|
## Output Structure
|
|
@@ -80,6 +139,13 @@ You **MUST** create a publication report:
|
|
|
80
139
|
- Repo: owner/repo
|
|
81
140
|
- Date: YYYY-MM-DD
|
|
82
141
|
|
|
142
|
+
## Tracking Issues
|
|
143
|
+
|
|
144
|
+
- PRD issue: #<number> (reused | created)
|
|
145
|
+
- Wave issue: #<number> (reused | created)
|
|
146
|
+
- Hierarchy: verified(<n> of <n>) | failed(<reason>)
|
|
147
|
+
- prd_status: written | failed(<reason>) | skipped(no PRD issue)
|
|
148
|
+
|
|
83
149
|
## Created Issues
|
|
84
150
|
|
|
85
151
|
| Story ID | Story Title | Issue URL | Labels | Milestone | Assignee |
|
|
@@ -92,7 +158,7 @@ You **MUST** create a publication report:
|
|
|
92
158
|
- Any skipped stories and why
|
|
93
159
|
- Any template or permission limitations
|
|
94
160
|
- Any manual follow-up needed
|
|
95
|
-
- Execution method used: `
|
|
161
|
+
- Execution method used: `gh-cli` or `github-mcp`
|
|
96
162
|
- Assisted-by value used for PR creation/issue closure (if applicable)
|
|
97
163
|
```
|
|
98
164
|
|
|
@@ -106,6 +172,9 @@ You **MUST** create a publication report:
|
|
|
106
172
|
|
|
107
173
|
1. You **MUST** read the user stories file.
|
|
108
174
|
2. You **MUST** ask clarifying questions and confirm the target repo.
|
|
109
|
-
3. You **MUST**
|
|
110
|
-
4. You **MUST**
|
|
111
|
-
5. You **MUST**
|
|
175
|
+
3. You **MUST** find or create the PRD and wave tracking issues before publishing any story; more than one match stops the run.
|
|
176
|
+
4. You **MUST** publish each story as a GitHub Issue by delegating to `github-ops` whenever possible, and attach it as a sub-issue of the wave issue.
|
|
177
|
+
5. You **MUST** attach the wave under the PRD issue, verify the hierarchy, and record the `hierarchy:` result.
|
|
178
|
+
6. You **MUST** create or edit the PRD issue's status comment so the wave's row reads `published`, and record `prd_status` in the publication report.
|
|
179
|
+
7. You **MUST** save the publication report with the tracking issue numbers and issue links.
|
|
180
|
+
8. You **MUST** inform the user that GitHub is now the source of truth for execution tracking.
|
|
@@ -91,13 +91,13 @@ Before merging any PR or branch, verify:
|
|
|
91
91
|
|
|
92
92
|
Choose the appropriate strategy based on context:
|
|
93
93
|
|
|
94
|
-
| Strategy | When to Use
|
|
95
|
-
| ---------------- |
|
|
96
|
-
| **
|
|
97
|
-
| **
|
|
98
|
-
| **Rebase merge** | Not part of the
|
|
94
|
+
| Strategy | When to Use | Command |
|
|
95
|
+
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------- |
|
|
96
|
+
| **Merge commit** | **Default for every PR.** Issue/story PRs → integration (planner) or `main` (user), and integration PRs → `main` (user). Preserves every commit. | `gh pr merge <pr> --merge --delete-branch` |
|
|
97
|
+
| **Squash merge** | Not part of the policy; use only when the user explicitly asks for a single-commit history on a specific PR. | `gh pr merge <pr> --squash --delete-branch` |
|
|
98
|
+
| **Rebase merge** | Not part of the policy; use only when the user explicitly approves it on a specific PR. | `gh pr merge <pr> --rebase` |
|
|
99
99
|
|
|
100
|
-
**Default**:
|
|
100
|
+
**Default**: Every PR merges by merge commit, so the per-task Conventional Commits survive to `main`. Issue/story PRs also delete the source branch. Planner handles integration targets, and the user handles `main`. Never squash or rebase unless the user asks for it on a specific PR.
|
|
101
101
|
|
|
102
102
|
### 6. Resolve Merge Conflicts
|
|
103
103
|
|
|
@@ -118,6 +118,7 @@ memo write \
|
|
|
118
118
|
--entry-type decision \
|
|
119
119
|
--source agent \
|
|
120
120
|
--provenance "<csv of episodic entry ids this consolidates, if any>" \
|
|
121
|
+
--on-duplicate create-new \
|
|
121
122
|
--json
|
|
122
123
|
```
|
|
123
124
|
|
|
@@ -166,7 +167,8 @@ A `semantic` entry with `--source agent` **MUST** carry `--provenance <csv>` unl
|
|
|
166
167
|
## Agent Mode Rules
|
|
167
168
|
|
|
168
169
|
- Always pass `--json` for parseable output
|
|
169
|
-
- Always pass `--on-duplicate
|
|
170
|
+
- Always pass `--on-duplicate` for writes; in `--json` mode memo-cli fails on a duplicate without it
|
|
171
|
+
- Pass `create-new` for distinct decisions, one entry per decision row (a feature's decision write-back); pass `consolidate` only when restating or updating the same decision, such as re-writing an entry after an amendment on the same story and commit to correct its rationale (D-78)
|
|
170
172
|
- Never log API keys or secrets
|
|
171
173
|
- Bulk delete is blocked in `--json` mode (safety guard)
|
|
172
174
|
|
|
@@ -81,6 +81,7 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
81
81
|
3. **Task synchronization:** Whenever a sub-task is completed, you **MUST** immediately mark `[x]` in:
|
|
82
82
|
- The local task file in `/workstream/`
|
|
83
83
|
- The GitHub Issue checklist
|
|
84
|
+
- The story's status comment on the GitHub Issue, kept current per the `implement` procedure's `### Status Comment` section — the procedure and the `github-ops` § Status comment template are referenced by name and never restated here; report each outcome as `status_comment:` and `wave_status:` in the closeout payload
|
|
84
85
|
4. **Branch + PR discipline (before coding):** You **MUST** follow `github-ops` conventions:
|
|
85
86
|
- Create branch per `github-ops` branch naming rules (e.g., `issue/42-short-description`, `story/S-003-short-description`)
|
|
86
87
|
- Open a Draft PR against the default branch unless a base branch override is provided. A PR requires at least one commit, so open it immediately after the first commit on the branch — never before. You **MUST NOT** continue past that first commit without the Draft PR open.
|
|
@@ -88,7 +89,7 @@ If the user provides a feature description or asks to create a PRD/spec/stories
|
|
|
88
89
|
- Use the `github-ops` PR description template (What / Why / How / Testing / Checklist)
|
|
89
90
|
- Include `Closes #<issue-number>` in the PR description
|
|
90
91
|
5. **Stop-gate rule:** If mode is `step-gated`, you **MUST** stop after each sub-task and request user approval.
|
|
91
|
-
6. **Do not close issue
|
|
92
|
+
6. **Do not close the issue:** You **MUST NOT** close the issue; GitHub closes it when the consolidated PR merges to main under the `planner`, and when the story PR itself merges to the default branch in single-issue work without a planner. Either way the closing PR targets the default branch and carries `Closes #<issue-number>`, and nobody closes it by hand. A story PR into an integration branch closes nothing, because GitHub ignores closing keywords on a PR whose base is not the default branch.
|
|
92
93
|
7. **Keep scope tight:** You **MUST** work only on the selected issue/stories unless the user explicitly expands scope.
|
|
93
94
|
8. **Update Relevant Files:** You **MUST** keep the task file's Relevant Files section accurate.
|
|
94
95
|
9. **English-only outputs:** You **MUST** produce English-only output for docs, comments, and generated content.
|
|
@@ -120,7 +121,7 @@ Follow `.kiro/steering/implement.md`:
|
|
|
120
121
|
- If HEAD is already a valid feature branch (matching `issue/*` or `story/*`), confirm the Draft PR exists and proceed. If the branch has no commits yet, no PR can exist — open it immediately after the first commit.
|
|
121
122
|
5. **memo intent (when memo is available):** Before writing any implementation code, run the memo-cli Availability Check and write the intent entry (see **memo-cli Integration → Intent Entry**). Record `memo_intent` as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`.
|
|
122
123
|
6. Execute one sub-task at a time in checklist order. For each behavioral sub-task, follow **test-first**: write/update tests first, verify they fail for the right reason, then implement to make them pass.
|
|
123
|
-
7. After each completed sub-task: mark `[x]` locally and in GitHub, pause for approval if step-gated.
|
|
124
|
+
7. After each completed sub-task: mark `[x]` locally and in GitHub, update the status comment per `implement` § Status Comment, pause for approval if step-gated.
|
|
124
125
|
8. When all sub-tasks are complete:
|
|
125
126
|
- Verify all acceptance criteria.
|
|
126
127
|
- Run mandatory quality gates and record results (`test`, `lint`, `format:check`, `typecheck`, `audit`; `validate` if available).
|
|
@@ -319,7 +320,7 @@ Before marking a Story/Issue done:
|
|
|
319
320
|
9. `/workstream` **SHOULD** be cleaned (active artifacts retained, obsolete artifacts archived/removed).
|
|
320
321
|
10. The memo intent and outcome writes **MUST** have been attempted when memo-cli is available (`memo write --kind episodic --session ISSUE-<n> --bank developer-memory …`, before PR conversion), and `memo_intent` / `memo_outcome` **MUST** be recorded as `written(<id>)`, `failed(<reason>)`, or `skipped(<reason>)`. A `failed` or `skipped` value does not block completion; an omitted field does.
|
|
321
322
|
11. PR **MUST** be ready, approved, and merged.
|
|
322
|
-
12. You **MUST NOT** close the GitHub Issue
|
|
323
|
+
12. You **MUST NOT** close the GitHub Issue; nobody closes it by hand. It closes when a PR against the default branch carrying `Closes #N` merges: under the `planner` that is the consolidated PR, and in single-issue work without a planner it is the story PR itself (rule 6).
|
|
323
324
|
13. For multi-story implementations, you **MUST** run a checklist cross-check between GitHub Issue tasks and `/workstream/tasks-*.md` and report any mismatch resolution.
|
|
324
325
|
|
|
325
326
|
---
|
|
@@ -337,6 +338,7 @@ For each run, return a compact status report with:
|
|
|
337
338
|
- Files updated in `/docs/` and ADR path (if created)
|
|
338
339
|
- Test results for the current step
|
|
339
340
|
- Quality gate results (`test`, `lint`, `format:check`, `typecheck`, `audit`)
|
|
341
|
+
- Status comment outcome (`status_comment`, `wave_status`)
|
|
340
342
|
- Next exact sub-task awaiting approval or currently executing
|
|
341
343
|
|
|
342
344
|
When finishing a story/issue execution cycle, return a **complete closeout summary** that includes:
|
|
@@ -381,6 +383,8 @@ workstream_files:
|
|
|
381
383
|
memo_intent: written(<id>) | failed(<reason>) | skipped(<reason>)
|
|
382
384
|
memo_outcome: written(<id>) | failed(<reason>) | skipped(<reason>)
|
|
383
385
|
checklist_sync: synced | mismatch-fixed | blocked
|
|
386
|
+
status_comment: written | failed(<reason>) | skipped(<reason>)
|
|
387
|
+
wave_status: written | failed(<reason>) | skipped(<reason>) | owned-by-planner
|
|
384
388
|
verifier_audit: run | blocked
|
|
385
389
|
fidelity_verdict: High | Medium | Low | none
|
|
386
390
|
highest_drift_impact: Critical | Major | Minor | None
|
|
@@ -395,5 +399,6 @@ Rules for this payload:
|
|
|
395
399
|
- Every field is required. Use `none`, `NOT RUN`, or `blocked` when a value does not exist.
|
|
396
400
|
- `memo_intent` and `memo_outcome` are always present. `skipped(<reason>)` (memo not installed, not configured, or unavailable in this session) and `failed(<reason>)` (the write was attempted and errored after one retry) are valid values that do not block the merge; `planner` treats an absent field as an incomplete story.
|
|
397
401
|
- `planner` may treat the story as incomplete if either marker or any required field is missing.
|
|
402
|
+
- `status_comment` and `wave_status` are always present; `skipped(<reason>)` is the floor, never an omission — a task list with no GitHub Issue reports `skipped(no issue)` for both (D-28). Under `planner` the wave comment belongs to the planner, so `wave_status: owned-by-planner` is the expected value in this agent's default subagent-delegation context; `written`, `skipped(no parent)` and `failed(<reason>)` come from the main-thread wave update defined in `implement`.
|
|
398
403
|
|
|
399
404
|
Do not dump full files unless explicitly requested.
|