agent-eng 0.3.0 → 0.4.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/package.json +1 -1
- package/src/init.js +2 -0
- package/src/templates/CLAUDE.md +1 -1
- package/src/templates/prompts/planner.md +19 -4
- package/src/templates/tickets/_backlog.md +35 -0
- package/src/templates/tickets/_template.md +1 -0
- package/src/templates/tickets/example/001-example-ticket.md +38 -0
package/package.json
CHANGED
package/src/init.js
CHANGED
package/src/templates/CLAUDE.md
CHANGED
|
@@ -29,7 +29,7 @@ This project separates AI-assisted work into six roles. Each role has a dedicate
|
|
|
29
29
|
- `architecture.yaml` — System architecture definition (components, connections, tiers)
|
|
30
30
|
- `orchestration.yaml` — Agent workflow definition (roles, outputs, connections)
|
|
31
31
|
- `specs/` — Feature specifications
|
|
32
|
-
- `tickets/` — Work items with
|
|
32
|
+
- `tickets/` — Work items organized by feature folder, with `_backlog.md` as the sprint board
|
|
33
33
|
- `conventions/` — Language and framework coding standards
|
|
34
34
|
- `prompts/` — System prompts for each agent role
|
|
35
35
|
|
|
@@ -21,24 +21,39 @@ You are a planner agent. Your role is to decompose specs and ADRs into actionabl
|
|
|
21
21
|
|
|
22
22
|
1. Read the spec or feature request
|
|
23
23
|
2. Identify the relevant ADRs and conventions
|
|
24
|
-
3.
|
|
24
|
+
3. Create a feature folder under `tickets/<feature-name>/`
|
|
25
|
+
4. Break the work into logical chunks:
|
|
25
26
|
- Start with infrastructure/setup if needed
|
|
26
27
|
- Core functionality next
|
|
27
28
|
- Edge cases and polish last
|
|
28
|
-
|
|
29
|
+
5. For each chunk, create a numbered ticket (`001-`, `002-`, ...) in the feature folder:
|
|
29
30
|
- Clear context linking to the spec
|
|
30
31
|
- A one-sentence goal
|
|
31
32
|
- Testable acceptance criteria (checkboxes)
|
|
32
33
|
- Explicit out-of-scope items
|
|
33
|
-
|
|
34
|
+
6. Update `tickets/_backlog.md` with the new tickets in priority order
|
|
35
|
+
7. Review the full set for gaps and dependencies
|
|
34
36
|
|
|
35
37
|
## Output Format
|
|
36
38
|
|
|
37
|
-
Use the ticket template from `tickets/_template.md
|
|
39
|
+
Use the ticket template from `tickets/_template.md`. Place tickets in feature folders:
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
tickets/
|
|
43
|
+
├── _backlog.md ← sprint board
|
|
44
|
+
├── _template.md ← ticket template
|
|
45
|
+
├── auth/
|
|
46
|
+
│ ├── 001-login-flow.md
|
|
47
|
+
│ └── 002-signup-flow.md
|
|
48
|
+
└── payments/
|
|
49
|
+
├── 001-checkout.md
|
|
50
|
+
└── 002-refund.md
|
|
51
|
+
```
|
|
38
52
|
|
|
39
53
|
```markdown
|
|
40
54
|
# Ticket: Title
|
|
41
55
|
|
|
56
|
+
**Feature:** feature-name
|
|
42
57
|
**Status:** Todo
|
|
43
58
|
**Priority:** P1
|
|
44
59
|
**Estimate:** M
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
# Backlog
|
|
2
|
+
|
|
3
|
+
Track and prioritize work across features. Move tickets between sections as they progress.
|
|
4
|
+
|
|
5
|
+
## Current Sprint
|
|
6
|
+
|
|
7
|
+
_Tickets actively being worked on this cycle._
|
|
8
|
+
|
|
9
|
+
| Ticket | Feature | Priority | Status | Assignee |
|
|
10
|
+
|--------|---------|----------|--------|----------|
|
|
11
|
+
| | | | | |
|
|
12
|
+
|
|
13
|
+
## Up Next
|
|
14
|
+
|
|
15
|
+
_Tickets ready to be picked up in the next cycle._
|
|
16
|
+
|
|
17
|
+
| Ticket | Feature | Priority | Estimate |
|
|
18
|
+
|--------|---------|----------|----------|
|
|
19
|
+
| | | | |
|
|
20
|
+
|
|
21
|
+
## Backlog
|
|
22
|
+
|
|
23
|
+
_Tickets that are planned but not yet scheduled._
|
|
24
|
+
|
|
25
|
+
| Ticket | Feature | Priority | Estimate |
|
|
26
|
+
|--------|---------|----------|----------|
|
|
27
|
+
| | | | |
|
|
28
|
+
|
|
29
|
+
## Done
|
|
30
|
+
|
|
31
|
+
_Completed tickets. Move here when done, newest first._
|
|
32
|
+
|
|
33
|
+
| Ticket | Feature | Completed |
|
|
34
|
+
|--------|---------|-----------|
|
|
35
|
+
| | | |
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
# Ticket: Example Ticket
|
|
2
|
+
|
|
3
|
+
**Feature:** example
|
|
4
|
+
**Status:** Todo
|
|
5
|
+
**Priority:** P1
|
|
6
|
+
**Estimate:** S
|
|
7
|
+
**Related:** ADR-0001
|
|
8
|
+
|
|
9
|
+
## Context
|
|
10
|
+
|
|
11
|
+
This is an example ticket inside a feature folder. Each feature gets its own directory under `tickets/`. Tickets within a feature are numbered sequentially (001, 002, ...) to indicate order.
|
|
12
|
+
|
|
13
|
+
## Goal
|
|
14
|
+
|
|
15
|
+
Demonstrate the ticket structure so new contributors know the format.
|
|
16
|
+
|
|
17
|
+
## Acceptance Criteria
|
|
18
|
+
|
|
19
|
+
- [ ] Criterion 1 — specific, testable condition
|
|
20
|
+
- [ ] Criterion 2 — specific, testable condition
|
|
21
|
+
- [ ] Tests pass
|
|
22
|
+
- [ ] No lint errors
|
|
23
|
+
|
|
24
|
+
## Out of Scope
|
|
25
|
+
|
|
26
|
+
Anything not directly related to this feature.
|
|
27
|
+
|
|
28
|
+
## Notes
|
|
29
|
+
|
|
30
|
+
Delete this example folder when you create your first real feature.
|
|
31
|
+
|
|
32
|
+
## Implementation Plan
|
|
33
|
+
|
|
34
|
+
_To be filled in by the executor before starting work._
|
|
35
|
+
|
|
36
|
+
1. Step 1
|
|
37
|
+
2. Step 2
|
|
38
|
+
3. Step 3
|