@igorlau/dotagents 1.0.10 → 1.0.11

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/README.md CHANGED
@@ -94,6 +94,7 @@ The following skills load when a task needs them:
94
94
  | `dot-debug` | Diagnose hard bugs with a feedback loop. |
95
95
  | `dot-grill-me` | Start an interview that sharpens a plan. |
96
96
  | `dot-grilling` | Run the interview method behind `dot-grill-me`. |
97
+ | `dot-roadmap` | Split a grilled plan into phases and self-contained tasks. |
97
98
  | `dot-handoff` | Summarize a conversation for another agent. |
98
99
  | `dot-writing-for-agents` | Write skills, `AGENTS.md`, and `CLAUDE.md` files. |
99
100
 
@@ -0,0 +1,125 @@
1
+ ---
2
+ name: dot-roadmap
3
+ description: Turn a grilled plan into a roadmap of phases, each split into self-contained tasks.
4
+ argument-hint: "Path to the plan, if it isn't in this conversation"
5
+ disable-model-invocation: true
6
+ ---
7
+
8
+ # Roadmap
9
+
10
+ A roadmap splits a plan into **phases**, and each phase into **tasks**. A phase ends on a **milestone**: an observable state where the system works and could ship. A task is **self-contained**: a fresh agent session can build it from its file alone, and a reviewer can judge its diff in one sitting.
11
+
12
+ ## Repository conventions first
13
+
14
+ Before you start, read what the repository defines: agent instructions (`AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, `.github/instructions/`, `.cursor/rules/`), project skills, `CONTRIBUTING.md`, style guides, linter and formatter configuration, and the patterns in the surrounding code. They take precedence over this skill: where they differ, follow the repository, and point out the difference instead of changing the repository's standard. Write tasks whose changes fit those conventions.
15
+
16
+ ## 1. Load the plan
17
+
18
+ Work from the plan in this conversation, usually the shared understanding a `dot-grill-me` session reached. If the user passed a path or URL, read it in full.
19
+
20
+ Synthesize; don't interview. If the plan still has unsettled decisions, list them and suggest `dot-grill-me` before you go on. Done when you can state the **destination** (what is true when the whole roadmap is done) and every decision the plan made.
21
+
22
+ ## 2. Gather facts
23
+
24
+ Read the code, tests, and configuration the plan touches. Note the modules each part of the plan reaches, the tests that already cover them, and any **prefactor**: a refactor that makes the later work easy. Done when you can name the files or modules each part of the plan changes.
25
+
26
+ ## 3. Cut phases
27
+
28
+ Group the work into phases, ordered so that:
29
+
30
+ - The first phase is a **tracer bullet**: the thinnest path through the whole system that proves the approach, so the riskiest unknown fails first.
31
+ - Prefactors come before the behavior that needs them.
32
+ - Each later phase builds on a milestone that already works.
33
+
34
+ Done when every phase has a milestone you can observe (a command's output, a passing test, a behavior in the UI), and the last milestone matches the destination.
35
+
36
+ ## 4. Split phases into tasks
37
+
38
+ Split each phase into tasks. Each task:
39
+
40
+ - Is a **vertical slice**: a narrow but complete path through every layer it needs, verifiable on its own.
41
+ - Keeps a refactor separate from a behavior change.
42
+ - Fits one fresh agent session and one reviewable diff, roughly a few hundred changed lines.
43
+ - Declares its **blockers**: the tasks that must be done first, by id (`2.3` is phase 2, task 3). A task without blockers can start now.
44
+
45
+ A **wide refactor**, one mechanical change that breaks many call sites at once, can't land as one green slice. Sequence it as **expand–contract**: add the new form beside the old, migrate callers in batches (one task each, blocked by the expand), then delete the old form in a task blocked by every batch.
46
+
47
+ Done when every requirement and decision from the plan belongs to exactly one task or to the roadmap's out-of-scope list, and every task has acceptance criteria that can fail.
48
+
49
+ ## 5. Review with the user
50
+
51
+ Show the breakdown compactly: each phase with its milestone, then its tasks as `id: title (blocked by: …) — goal`. Ask:
52
+
53
+ - Is the granularity right, or should some tasks merge or split?
54
+ - Does each blocker genuinely gate its task?
55
+ - Is anything in the plan missing, or in the wrong phase?
56
+
57
+ Iterate until the user approves. Write no files before approval.
58
+
59
+ ## 6. Write the roadmap
60
+
61
+ Write to `.tmp/roadmaps/<roadmap-slug>/` at the repository root. First run `git check-ignore -q .tmp`: if `.tmp` isn't ignored, stop and tell the user rather than editing `.gitignore`.
62
+
63
+ ```
64
+ .tmp/roadmaps/<roadmap-slug>/
65
+ ├── README.md
66
+ ├── 01-<phase-slug>/
67
+ │ ├── 01-<task-slug>.md
68
+ │ └── 02-<task-slug>.md
69
+ └── 02-<phase-slug>/
70
+ └── 01-<task-slug>.md
71
+ ```
72
+
73
+ `README.md` is the index and the single source of truth for decisions; task files link to it instead of restating them:
74
+
75
+ ```markdown
76
+ # <Roadmap title>
77
+
78
+ **Destination:** <what is true when the roadmap is done>
79
+
80
+ ## Decisions
81
+
82
+ - <decision from the plan, one line each, with the reason when it isn't obvious>
83
+
84
+ ## Out of scope
85
+
86
+ - <work the plan ruled out>
87
+
88
+ ## Phases
89
+
90
+ ### 1. <Phase title>
91
+
92
+ **Milestone:** <observable state>
93
+
94
+ - [ ] [1.1 <Task title>](01-<phase-slug>/01-<task-slug>.md) (blocked by: none)
95
+ - [ ] [1.2 <Task title>](01-<phase-slug>/02-<task-slug>.md) (blocked by: 1.1)
96
+ ```
97
+
98
+ Each task file:
99
+
100
+ ```markdown
101
+ # <id>: <Task title>
102
+
103
+ **Roadmap:** [<Roadmap title>](../README.md)
104
+ **Goal:** <one sentence: the behavior this task makes work>
105
+ **Blocked by:** <ids, or "none">
106
+
107
+ ## Requirements
108
+
109
+ - <what the change must do, specific enough to build without the conversation>
110
+ - <files or modules it touches, when known>
111
+
112
+ ## Out of scope
113
+
114
+ - <nearby work that belongs to another task, with its id>
115
+
116
+ ## Acceptance criteria
117
+
118
+ - [ ] <checkable condition>
119
+
120
+ ## Verify
121
+
122
+ <the command or observation that proves the acceptance criteria>
123
+ ```
124
+
125
+ Done when every task file exists, `README.md` links each one, and each task reads complete without this conversation. End by telling the user the roadmap's path and the tasks they can start now.
@@ -1 +1 @@
1
- {"commit":"9ea2648"}
1
+ {"commit":"a676226"}
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@igorlau/dotagents",
3
- "version": "1.0.10",
3
+ "version": "1.0.11",
4
4
  "description": "Install a curated set of agent skills and rules into Claude Code, Codex, and GitHub Copilot.",
5
5
  "license": "MIT",
6
6
  "repository": {