@llipe.com/dev-tasks 0.6.1 → 0.6.5
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 +294 -0
- package/.claude/agents/github-ops.md +407 -0
- package/.claude/agents/housekeeping.md +109 -0
- package/.claude/agents/technical-writer.md +390 -0
- package/.claude/agents/ux-engineer.md +184 -0
- package/.claude/agents/verifier.md +276 -0
- package/.claude/commands/developer.md +272 -0
- package/.claude/commands/github-ops.md +10 -0
- package/.claude/commands/housekeeping.md +10 -0
- package/.claude/commands/planner.md +506 -0
- package/.claude/commands/product-engineer.md +263 -0
- package/.claude/commands/technical-writer.md +10 -0
- package/.claude/commands/ux-engineer.md +10 -0
- package/.claude/commands/verifier-audit.md +10 -0
- package/.claude/commands/verifier-design.md +10 -0
- package/.claude/hooks/git-guard.sh +95 -0
- package/.claude/skills/activity-contract-test-design/SKILL.md +122 -0
- package/.claude/skills/activity-drift-reconciliation/SKILL.md +133 -0
- package/.claude/skills/activity-e2e-test-design/SKILL.md +124 -0
- package/.claude/skills/activity-edge-case-refinement/SKILL.md +146 -0
- package/.claude/skills/activity-generate-spec/SKILL.md +137 -0
- package/.claude/skills/activity-generate-stories/SKILL.md +243 -0
- package/.claude/skills/activity-init/SKILL.md +162 -0
- package/.claude/skills/activity-publish-github/SKILL.md +116 -0
- package/.claude/skills/activity-random-test-tactics/SKILL.md +181 -0
- package/.claude/skills/activity-refine/SKILL.md +236 -0
- package/.claude/skills/git-ops/SKILL.md +221 -0
- package/.claude/skills/implement/SKILL.md +129 -0
- package/.claude/skills/memo-cli-usage/REFERENCE.md +798 -0
- package/.claude/skills/memo-cli-usage/SKILL.md +144 -0
- package/.claude/skills/plan/SKILL.md +145 -0
- package/.claude/skills/webapp-mockup/SKILL.md +76 -0
- package/.claude/skills/webapp-mockup/scripts/scaffold-mockup.sh +469 -0
- package/.github/agents/developer.agent.md +293 -0
- package/.github/agents/github-ops.agent.md +416 -0
- package/.github/agents/housekeeping.agent.md +109 -0
- package/.github/agents/planner.agent.md +496 -0
- package/.github/agents/product-engineer.agent.md +262 -0
- package/.github/agents/technical-writer.agent.md +389 -0
- package/.github/agents/ux-engineer.agent.md +183 -0
- package/.github/agents/verifier.agent.md +275 -0
- package/.github/instructions/domain/nextjs-pages-components.instructions.md +375 -0
- package/.github/instructions/implement.instructions.md +128 -0
- package/.github/instructions/plan.instructions.md +144 -0
- package/.github/prompts/developer-execute.prompt.md +13 -0
- package/.github/prompts/github-ops.prompt.md +16 -0
- package/.github/prompts/housekeeping.prompt.md +16 -0
- package/.github/prompts/planner-resume.prompt.md +13 -0
- package/.github/prompts/planner.prompt.md +18 -0
- package/.github/prompts/product-engineer-feature.prompt.md +21 -0
- package/.github/prompts/product-engineer-init.prompt.md +16 -0
- package/.github/prompts/product-engineer-issue.prompt.md +19 -0
- package/.github/prompts/technical-writer.prompt.md +21 -0
- package/.github/prompts/ux-engineer.prompt.md +14 -0
- package/.github/prompts/verifier-audit.prompt.md +33 -0
- package/.github/prompts/verifier-design.prompt.md +28 -0
- package/.github/skills/activity-contract-test-design/SKILL.md +117 -0
- package/.github/skills/activity-drift-reconciliation/SKILL.md +128 -0
- package/.github/skills/activity-e2e-test-design/SKILL.md +119 -0
- package/.github/skills/activity-edge-case-refinement/SKILL.md +141 -0
- package/.github/skills/activity-generate-spec/SKILL.md +132 -0
- package/.github/skills/activity-generate-stories/SKILL.md +238 -0
- package/.github/skills/activity-init/SKILL.md +157 -0
- package/.github/skills/activity-publish-github/SKILL.md +111 -0
- package/.github/skills/activity-random-test-tactics/SKILL.md +176 -0
- package/.github/skills/activity-refine/SKILL.md +231 -0
- package/.github/skills/git-ops/SKILL.md +216 -0
- package/.github/skills/memo-cli-usage/REFERENCE.md +798 -0
- package/.github/skills/memo-cli-usage/SKILL.md +144 -0
- package/.github/skills/webapp-mockup/SKILL.md +71 -0
- package/.github/skills/webapp-mockup/scripts/scaffold-mockup.sh +469 -0
- package/.kiro/agents/developer.md +305 -0
- package/.kiro/agents/github-ops.md +428 -0
- package/.kiro/agents/housekeeping.md +122 -0
- package/.kiro/agents/planner.md +530 -0
- package/.kiro/agents/product-engineer.md +294 -0
- package/.kiro/agents/technical-writer.md +408 -0
- package/.kiro/agents/ux-engineer.md +200 -0
- package/.kiro/agents/verifier.md +275 -0
- package/.kiro/hooks/git-guard.json +16 -0
- package/.kiro/hooks/scripts/git-guard.sh +116 -0
- package/.kiro/skills/activity-contract-test-design/SKILL.md +122 -0
- package/.kiro/skills/activity-drift-reconciliation/SKILL.md +133 -0
- package/.kiro/skills/activity-e2e-test-design/SKILL.md +124 -0
- package/.kiro/skills/activity-edge-case-refinement/SKILL.md +146 -0
- package/.kiro/skills/activity-generate-spec/SKILL.md +137 -0
- package/.kiro/skills/activity-generate-stories/SKILL.md +243 -0
- package/.kiro/skills/activity-init/SKILL.md +162 -0
- package/.kiro/skills/activity-publish-github/SKILL.md +116 -0
- package/.kiro/skills/activity-random-test-tactics/SKILL.md +181 -0
- package/.kiro/skills/activity-refine/SKILL.md +236 -0
- package/.kiro/skills/git-ops/SKILL.md +221 -0
- package/.kiro/skills/memo-cli-usage/REFERENCE.md +798 -0
- package/.kiro/skills/memo-cli-usage/SKILL.md +144 -0
- package/.kiro/skills/webapp-mockup/SKILL.md +76 -0
- package/.kiro/steering/git-guard-notice.md +11 -0
- package/.kiro/steering/implement.md +129 -0
- package/.kiro/steering/nextjs-pages-components.md +376 -0
- package/.kiro/steering/plan.md +145 -0
- package/AGENTS.md +122 -0
- package/CHANGELOG.md +40 -2
- package/CLAUDE.md +94 -0
- package/README.md +33 -18
- package/dist/adapters/cli/extract-all.js +4 -4
- package/dist/adapters/cli/extract-component.d.ts +1 -1
- package/dist/adapters/cli/extract-component.js +4 -4
- package/dist/adapters/cli/parse-args.d.ts +1 -0
- package/dist/adapters/cli/parse-args.d.ts.map +1 -1
- package/dist/adapters/cli/parse-args.js +4 -0
- package/dist/adapters/cli/parse-args.js.map +1 -1
- package/dist/bin/dev-tasks.js +23 -9
- package/dist/bin/dev-tasks.js.map +1 -1
- package/dist/bin/dt.js +3 -3
- package/dist/core/distribution/index.d.ts +5 -3
- package/dist/core/distribution/index.d.ts.map +1 -1
- package/dist/core/distribution/index.js +3 -2
- package/dist/core/distribution/index.js.map +1 -1
- package/dist/core/distribution/install.d.ts +20 -8
- package/dist/core/distribution/install.d.ts.map +1 -1
- package/dist/core/distribution/install.js +76 -36
- package/dist/core/distribution/install.js.map +1 -1
- package/dist/core/distribution/manifest.d.ts +25 -2
- package/dist/core/distribution/manifest.d.ts.map +1 -1
- package/dist/core/distribution/manifest.js +29 -2
- package/dist/core/distribution/manifest.js.map +1 -1
- package/dist/core/distribution/migrate.d.ts +6 -3
- package/dist/core/distribution/migrate.d.ts.map +1 -1
- package/dist/core/distribution/migrate.js +21 -19
- package/dist/core/distribution/migrate.js.map +1 -1
- package/dist/core/distribution/profiles.d.ts +30 -0
- package/dist/core/distribution/profiles.d.ts.map +1 -0
- package/dist/core/distribution/profiles.js +57 -0
- package/dist/core/distribution/profiles.js.map +1 -0
- package/dist/core/distribution/update.d.ts +6 -4
- package/dist/core/distribution/update.d.ts.map +1 -1
- package/dist/core/distribution/update.js +22 -22
- package/dist/core/distribution/update.js.map +1 -1
- package/dist/core/extract/component.d.ts +9 -9
- package/dist/core/extract/component.js +5 -5
- package/dist/core/extract/report.d.ts +1 -1
- package/dist/core/extract/report.js +1 -1
- package/package.json +37 -18
- package/skills/.gitkeep +0 -0
|
@@ -0,0 +1,144 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: memo-cli-usage
|
|
3
|
+
description: "Read and write architectural decisions to the shared memo-cli knowledge base. Use when recording or restoring cross-session context."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# memo-cli Usage — Quick Reference
|
|
7
|
+
|
|
8
|
+
Operate `memo-cli` for reading and writing architectural decisions in a shared Qdrant vector database. For full CLI documentation (all flags, configuration, admin operations, schema details), see [`REFERENCE.md`](./REFERENCE.md).
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## Setup Validation
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
memo setup validate # exit 0 = configured correctly
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
If validation fails, run: `memo setup init --repo <repo> --org <org> --domain <domain>`
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
## Session Start — Restore Context
|
|
23
|
+
|
|
24
|
+
Run before writing any code:
|
|
25
|
+
|
|
26
|
+
```bash
|
|
27
|
+
memo list --limit 20 --json
|
|
28
|
+
memo tags list --sort frequency --json
|
|
29
|
+
memo search "<current task description>" --limit 10 --json
|
|
30
|
+
memo search "<key contract or dependency>" --scope related --limit 5 --json
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
Synthesize findings into:
|
|
34
|
+
|
|
35
|
+
- Constraints to preserve
|
|
36
|
+
- Rejected alternatives to avoid
|
|
37
|
+
- Contracts/boundaries that must remain stable
|
|
38
|
+
- Sensitive files/modules to treat carefully
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
## Writing Entries
|
|
43
|
+
|
|
44
|
+
### Intent Entry (before starting a story/task)
|
|
45
|
+
|
|
46
|
+
```bash
|
|
47
|
+
memo write \
|
|
48
|
+
--rationale "Context: Starting ISSUE-<##> because <trigger>. Decision: implement via <approach>, preserving <constraints>. Impact: affects <modules/contracts>." \
|
|
49
|
+
--tags "<domain>,issue-<number>,intent,<impact-tag>" \
|
|
50
|
+
--entry-type decision \
|
|
51
|
+
--source agent \
|
|
52
|
+
--story "ISSUE-<number>" \
|
|
53
|
+
--on-duplicate consolidate \
|
|
54
|
+
--json
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
### Outcome Entry (after completing a story/task)
|
|
58
|
+
|
|
59
|
+
```bash
|
|
60
|
+
memo write \
|
|
61
|
+
--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>." \
|
|
62
|
+
--tags "<domain>,issue-<number>,outcome,gates-pass" \
|
|
63
|
+
--entry-type decision \
|
|
64
|
+
--source agent \
|
|
65
|
+
--commit "$(git rev-parse HEAD)" \
|
|
66
|
+
--story "ISSUE-<number>" \
|
|
67
|
+
--files "<key files modified>" \
|
|
68
|
+
--on-duplicate consolidate \
|
|
69
|
+
--json
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
### Decision Entry (architectural choices)
|
|
73
|
+
|
|
74
|
+
```bash
|
|
75
|
+
memo write \
|
|
76
|
+
--rationale "Context: <situation>. Decision: <what was chosen>. Rationale: <why this over alternatives>." \
|
|
77
|
+
--tags "<domain>,<technology>,decision" \
|
|
78
|
+
--entry-type decision \
|
|
79
|
+
--source agent \
|
|
80
|
+
--json
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
## Entry Types
|
|
86
|
+
|
|
87
|
+
| Type | Use For |
|
|
88
|
+
| ------------------- | --------------------------------------------- |
|
|
89
|
+
| `decision` | Architectural/design choices, intent, outcome |
|
|
90
|
+
| `integration_point` | Cross-service contracts, API boundaries |
|
|
91
|
+
| `structure` | Module layout, naming conventions |
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## Tag Rules
|
|
96
|
+
|
|
97
|
+
- Kebab-case only: `rate-limiting` not `rateLimiting`
|
|
98
|
+
- 4-5 tags per entry across layers: domain, work-item, lifecycle, impact, boundary
|
|
99
|
+
- Check existing tags first: `memo tags list --sort frequency --json`
|
|
100
|
+
- Reuse over inventing new tags
|
|
101
|
+
|
|
102
|
+
---
|
|
103
|
+
|
|
104
|
+
## When to Write
|
|
105
|
+
|
|
106
|
+
- Choosing a library, framework, or architecture pattern
|
|
107
|
+
- Changing config files (explain why)
|
|
108
|
+
- Modifying core abstractions, schemas, entry points
|
|
109
|
+
- Establishing naming/layout conventions
|
|
110
|
+
- Discovering constraints (API limits, platform quirks)
|
|
111
|
+
- Starting/completing a story (intent/outcome)
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
|
|
115
|
+
## When to Search
|
|
116
|
+
|
|
117
|
+
- Before making design choices: `memo search "<topic>" --json`
|
|
118
|
+
- Before touching unfamiliar files: `memo search "<filename>" --json`
|
|
119
|
+
- Cross-repo context: `memo search "<query>" --scope related --json`
|
|
120
|
+
|
|
121
|
+
---
|
|
122
|
+
|
|
123
|
+
## Agent Mode Rules
|
|
124
|
+
|
|
125
|
+
- Always pass `--json` for parseable output
|
|
126
|
+
- Always pass `--on-duplicate consolidate` for writes
|
|
127
|
+
- Never log API keys or secrets
|
|
128
|
+
- Bulk delete is blocked in `--json` mode (safety guard)
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## Quick Command Card
|
|
133
|
+
|
|
134
|
+
```
|
|
135
|
+
memo setup validate # Verify config
|
|
136
|
+
memo write --rationale "..." --tags "a,b,c" --json # Record decision
|
|
137
|
+
memo search "query" [--scope related] --json # Semantic search
|
|
138
|
+
memo list [--limit N] --json # Browse recent
|
|
139
|
+
memo tags list [--sort frequency] --json # Discover tags
|
|
140
|
+
memo inspect --json # Global facets
|
|
141
|
+
memo delete --id <uuid> --json # Delete entry
|
|
142
|
+
```
|
|
143
|
+
|
|
144
|
+
> For full flag documentation, admin operations, environment setup, and detailed examples, read [`REFERENCE.md`](./REFERENCE.md).
|
|
@@ -0,0 +1,76 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: webapp-mockup
|
|
3
|
+
description: "Scaffold and generate runnable React mockups for UX testing. Use when prototyping UI before full implementation."
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Webapp Mockup Skill
|
|
7
|
+
|
|
8
|
+
Purpose
|
|
9
|
+
|
|
10
|
+
- Generate consistent, runnable React mockups for feature discovery and UI/functionality gap analysis.
|
|
11
|
+
- Produce partial, high-signal mockups with realistic UI artifacts: components, texts, transitions, popups, warnings, inputs, and validations.
|
|
12
|
+
|
|
13
|
+
When to use
|
|
14
|
+
|
|
15
|
+
- User asks to visualize a potential UI before full implementation.
|
|
16
|
+
- Team needs a browsable prototype to identify missing requirements.
|
|
17
|
+
- A feature section is still exploratory and should not include full backend flow.
|
|
18
|
+
|
|
19
|
+
Required behavior
|
|
20
|
+
|
|
21
|
+
1. Folder layout
|
|
22
|
+
|
|
23
|
+
- Create mockups only under:
|
|
24
|
+
- /mockups/mockup-<feature>-<num>
|
|
25
|
+
- Keep each mockup self-contained and runnable with npm scripts.
|
|
26
|
+
|
|
27
|
+
2. Color palette rule
|
|
28
|
+
|
|
29
|
+
- If the project or user has not defined a palette, ask for one.
|
|
30
|
+
- Default fallback palette source:
|
|
31
|
+
- https://colorhunt.co/palette/281c594e8d9c85c79aedf7bd
|
|
32
|
+
|
|
33
|
+
3. UI coverage requirements
|
|
34
|
+
|
|
35
|
+
- Include:
|
|
36
|
+
- Core components (cards, buttons, inputs, labels)
|
|
37
|
+
- Meaningful UI text and microcopy
|
|
38
|
+
- Transition behavior (section reveal, popup open/close)
|
|
39
|
+
- Popup/dialog examples
|
|
40
|
+
- Warning and error states
|
|
41
|
+
- Input validation states and messages
|
|
42
|
+
- No need to complete entire flow.
|
|
43
|
+
- If only a section is implemented, add a visible banner with instructions indicating this is a partial mockup and where to continue.
|
|
44
|
+
|
|
45
|
+
4. CSS references
|
|
46
|
+
|
|
47
|
+
- Ensure CSS files are referenced correctly from app entry/components.
|
|
48
|
+
- Keep any additional stylesheet imports explicit.
|
|
49
|
+
|
|
50
|
+
5. Consistency via scaffold script
|
|
51
|
+
|
|
52
|
+
- Use:
|
|
53
|
+
- ./.github/skills/webapp-mockup/scripts/scaffold-mockup.sh <feature> <num> [palette_url]
|
|
54
|
+
- This script must be the default path for creating new mockups to keep structure and baseline behavior consistent.
|
|
55
|
+
- The scaffold path must remain non-interactive so agents can run it without manual terminal confirmation.
|
|
56
|
+
|
|
57
|
+
Operational workflow
|
|
58
|
+
|
|
59
|
+
1. Confirm feature slug and mockup number.
|
|
60
|
+
2. Confirm palette or apply fallback URL.
|
|
61
|
+
3. Run scaffold script.
|
|
62
|
+
|
|
63
|
+
- The script is designed to run non-interactively in agent terminal sessions.
|
|
64
|
+
|
|
65
|
+
4. Implement or adjust the specific mockup section requested.
|
|
66
|
+
5. Verify app runs with npm run dev.
|
|
67
|
+
6. Summarize what is mocked vs intentionally not implemented.
|
|
68
|
+
|
|
69
|
+
Acceptance checklist
|
|
70
|
+
|
|
71
|
+
- Mockup path follows /mockups/mockup-<feature>-<num>
|
|
72
|
+
- App is runnable locally
|
|
73
|
+
- Palette is user-defined or fallback applied
|
|
74
|
+
- Banner exists for partial implementation
|
|
75
|
+
- Includes inputs + validations + warnings + popup + transitions
|
|
76
|
+
- CSS references are present and valid
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: always
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Git Guard — Three Invariants
|
|
6
|
+
|
|
7
|
+
1. No agent may push or merge into the default branch `main`.
|
|
8
|
+
2. `git commit` messages must follow Conventional Commits.
|
|
9
|
+
3. `gh issue`/`pr create|edit|comment|review` must use `--body-file`, never inline `--body`.
|
|
10
|
+
|
|
11
|
+
**Enforcement backstop:** Treat human PR review as the actual gate for these rules on Kiro. The hook (`.kiro/hooks/git-guard.json`) is best-effort due to a known upstream limitation.
|
|
@@ -0,0 +1,129 @@
|
|
|
1
|
+
---
|
|
2
|
+
inclusion: fileMatch
|
|
3
|
+
fileMatchPattern: "workstream/**/tasks-*.md"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Activity: Implement Task List
|
|
7
|
+
|
|
8
|
+
> **RFC 2119 Notice:** The key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY**, and **OPTIONAL** in this document are to be interpreted as described in [RFC 2119](https://www.rfc-editor.org/rfc/rfc2119).
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
|
|
12
|
+
Execute a task list step-by-step with strict sequencing, proper branching, PR workflow, GitHub Issue synchronization, and user approval gates.
|
|
13
|
+
|
|
14
|
+
This is the **single source of truth** for execution rules. All agents and workflows that perform implementation **MUST** follow these rules.
|
|
15
|
+
|
|
16
|
+
## Context
|
|
17
|
+
|
|
18
|
+
This activity assumes:
|
|
19
|
+
|
|
20
|
+
- A task list file exists in `/workstream/tasks-*.md`.
|
|
21
|
+
- The corresponding GitHub Issue exists and includes a checklist.
|
|
22
|
+
- GitHub is the source of truth for execution status.
|
|
23
|
+
|
|
24
|
+
## Package Manager and Command Standards
|
|
25
|
+
|
|
26
|
+
- For JavaScript/TypeScript repositories, you **MUST** prefer `pnpm` over `npm` for dependency and script commands.
|
|
27
|
+
- You **MAY** use `npm` only when `pnpm` is unavailable or the project is explicitly npm-locked.
|
|
28
|
+
- For JS/TS repositories, quality and test execution **MUST** use canonical `package.json` script names where available: `lint`, `format:check`, `typecheck`, `test`, `audit`, and `validate`.
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
## Before Starting Work
|
|
33
|
+
|
|
34
|
+
1. You **MUST** confirm the GitHub Issue is open.
|
|
35
|
+
2. You **MUST** create a new branch from the latest default branch by delegating branch naming and creation to `github-ops` whenever possible.
|
|
36
|
+
- Branch format: `issue/<issue-number>-<short-description>` or `story/<id>-<short-description>`
|
|
37
|
+
3. You **MUST** open a **draft Pull Request** by delegating to `github-ops` whenever possible.
|
|
38
|
+
- Base branch is the default branch unless an orchestrating caller explicitly provides a base-branch override.
|
|
39
|
+
- PR title **MUST** follow Conventional Commits (e.g., `feat: implement issue 37`).
|
|
40
|
+
- PR description **MUST** include `Closes #<issue-number>`.
|
|
41
|
+
4. You **MUST** ensure the task list in the GitHub Issue matches the local `/workstream/tasks-*.md` file.
|
|
42
|
+
|
|
43
|
+
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.
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
## During Implementation
|
|
48
|
+
|
|
49
|
+
### Step-by-Step Execution
|
|
50
|
+
|
|
51
|
+
- You **MUST** execute **one sub-task at a time**.
|
|
52
|
+
- You **MUST NOT** start the next sub-task until the user grants permission (says "yes" or "y").
|
|
53
|
+
- After completing each sub-task, you **MUST** immediately:
|
|
54
|
+
1. Mark it `[x]` in the local task file.
|
|
55
|
+
2. Mark it `[x]` in the GitHub Issue checklist.
|
|
56
|
+
3. Stop and wait for user approval before proceeding.
|
|
57
|
+
|
|
58
|
+
### Parent Task Completion
|
|
59
|
+
|
|
60
|
+
- When **all** sub-tasks under a parent task are `[x]`, you **MUST** also mark the **parent task** as `[x]`.
|
|
61
|
+
|
|
62
|
+
### Task List Maintenance
|
|
63
|
+
|
|
64
|
+
- You **MUST** regularly update the task list file after finishing significant work.
|
|
65
|
+
- You **MUST** add newly discovered tasks as they emerge.
|
|
66
|
+
- You **MUST** keep the "Relevant Files" section accurate and up to date with every file created or modified.
|
|
67
|
+
- You **MUST** keep the local task list and the GitHub Issue checklist aligned at all times.
|
|
68
|
+
- If drift is detected between local and GitHub, you **MUST** reconcile immediately and report the reconciliation.
|
|
69
|
+
- If schema/data-model changes are in scope, migration artifacts **MUST** be tracked in the task list unless an explicit opt-out rationale is documented.
|
|
70
|
+
|
|
71
|
+
### Progress Updates
|
|
72
|
+
|
|
73
|
+
- You **SHOULD** add brief issue or PR comments for major milestones or meaningful changes.
|
|
74
|
+
- You **SHOULD** route issue/PR comment updates through `github-ops` whenever possible.
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
## Before Closing a Story/Issue
|
|
79
|
+
|
|
80
|
+
1. All acceptance criteria **MUST** be verified.
|
|
81
|
+
2. All tests listed in the checklist **MUST** be completed and passing.
|
|
82
|
+
3. The following quality gates **MUST** be completed and passing before completion:
|
|
83
|
+
- `test`
|
|
84
|
+
- `lint`
|
|
85
|
+
- `format:check`
|
|
86
|
+
- `typecheck`
|
|
87
|
+
- `audit`
|
|
88
|
+
4. For schema/data-model changes, migration handling **MUST** satisfy all of the following:
|
|
89
|
+
- migration artifact created (unless documented opt-out)
|
|
90
|
+
- rollback/impact notes captured
|
|
91
|
+
- explicit user confirmation obtained before any migration apply command
|
|
92
|
+
- apply step executed only after user confirmation
|
|
93
|
+
- post-apply verification recorded
|
|
94
|
+
5. `technical-writer` validation **MUST** include a drift/stale-doc check report, and completion **MUST NOT** proceed while unresolved drift remains.
|
|
95
|
+
6. 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.
|
|
96
|
+
7. The PR **MUST** be converted from draft to ready for review.
|
|
97
|
+
8. The PR **MUST** be approved by the appropriate reviewer per the merge authority policy in `github-ops`:
|
|
98
|
+
- PRs targeting an **integration branch**: `planner` reviews and approves.
|
|
99
|
+
- PRs targeting **`main`**: the **user** reviews and approves.
|
|
100
|
+
9. The PR **MUST** be merged by the authorized party (planner for integration branches, user for `main`).
|
|
101
|
+
10. You **MUST NOT** close the GitHub Issue until the PR is approved **AND** merged.
|
|
102
|
+
11. You **MUST NOT** close the issue while the PR is still in draft or pending review.
|
|
103
|
+
12. You **MUST** notify the user when the PR is ready for review — explicitly inform them so they can review and merge.
|
|
104
|
+
|
|
105
|
+
---
|
|
106
|
+
|
|
107
|
+
## GitHub Execution Rules Summary
|
|
108
|
+
|
|
109
|
+
| Phase | Rule |
|
|
110
|
+
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
111
|
+
| **Before coding** | Confirm issue open → Create branch (`github-ops`) → Open draft PR (`github-ops`) → Sync checklists |
|
|
112
|
+
| **During coding** | One sub-task at a time → Mark `[x]` locally + GitHub → Wait for approval |
|
|
113
|
+
| **Before closing** | All ACs verified → Quality gates pass (test/lint/format/typecheck/audit) → migration confirmation/apply/verify (when applicable) → docs drift check clear → verifier audit run + summary posted (non-blocking on drift) → PR ready → Approved → Merged → Then close issue |
|
|
114
|
+
|
|
115
|
+
---
|
|
116
|
+
|
|
117
|
+
## Output
|
|
118
|
+
|
|
119
|
+
- Keep all changes and status updates in GitHub and `/workstream/tasks-*.md`.
|
|
120
|
+
- You **MUST** check which sub-task is next before starting work.
|
|
121
|
+
- After implementing a sub-task, you **MUST** update the file and then pause for user approval.
|
|
122
|
+
|
|
123
|
+
## Final Instructions
|
|
124
|
+
|
|
125
|
+
1. You **MUST** always respect the task list execution order.
|
|
126
|
+
2. You **MUST** keep the GitHub Issue updated with checklist and progress comments.
|
|
127
|
+
3. You **MUST** ensure branch, PR, and issue naming follow `github-ops` conventions.
|
|
128
|
+
4. You **MUST** stop after each sub-task and request user approval.
|
|
129
|
+
5. You **MUST NOT** close a GitHub Issue without confirming the PR has been reviewed, approved, and merged.
|