nightralph 0.0.34 → 0.0.35
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.
|
@@ -6,18 +6,26 @@ Issues and specs for this repo live as markdown files in `.scratch/`.
|
|
|
6
6
|
|
|
7
7
|
- One feature per directory: `.scratch/<feature-slug>/`
|
|
8
8
|
- The spec is `.scratch/<feature-slug>/spec.md`
|
|
9
|
-
- Implementation issues are one file per ticket at
|
|
10
|
-
-
|
|
11
|
-
|
|
12
|
-
-
|
|
9
|
+
- Implementation issues are one file per ticket at
|
|
10
|
+
`.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01`,
|
|
11
|
+
never a single combined tickets file
|
|
12
|
+
- Triage state is recorded as a `**Status:**` line near the top of each
|
|
13
|
+
issue file (see `triage-labels.md` for the role strings)
|
|
14
|
+
- Dependencies are recorded as a `**Blocked by:**` line near the top of
|
|
15
|
+
each issue file, listing the numbers of the tickets that must complete
|
|
16
|
+
first, or `None`
|
|
17
|
+
- Comments and conversation history append to the bottom of the file under
|
|
18
|
+
a `## Comments` heading
|
|
13
19
|
|
|
14
20
|
## When a skill says "publish to the issue tracker"
|
|
15
21
|
|
|
16
|
-
Create a new file under `.scratch/<feature-slug>/` (creating the directory
|
|
22
|
+
Create a new file under `.scratch/<feature-slug>/` (creating the directory
|
|
23
|
+
if needed).
|
|
17
24
|
|
|
18
25
|
## When a skill says "fetch the relevant ticket"
|
|
19
26
|
|
|
20
|
-
Read the file at the referenced path. The user will normally pass the path
|
|
27
|
+
Read the file at the referenced path. The user will normally pass the path
|
|
28
|
+
or the issue number directly.
|
|
21
29
|
|
|
22
30
|
## Tickets are executed within hours, not weeks
|
|
23
31
|
|
|
@@ -60,6 +60,8 @@ Iterate until the user approves the breakdown.
|
|
|
60
60
|
Publish the approved tickets. **How** depends on the tracker `npx nightralph init` configured; the tickets are the same either way, only the shape of the blocking edges changes:
|
|
61
61
|
|
|
62
62
|
- **Local files** → write one file per ticket under `.scratch/<feature-slug>/issues/<NN>-<slug>.md`, numbered from `01` in dependency order (blockers first). Each file's "Blocked by" lists the numbers/titles it depends on. Use the per-ticket file template below: one ticket per file, never a single combined file.
|
|
63
|
+
- Set every local ticket to `**Status:** ready-for-agent` so nightralph can
|
|
64
|
+
run it immediately. Do not publish local tickets as `needs-triage`.
|
|
63
65
|
- **A real issue tracker (GitHub, Linear, …)** → publish one issue per ticket in dependency order (blockers first) so each ticket's blocking edges can reference real identifiers. Use the platform's native blocking / sub-issue relationship where it has one; otherwise set each ticket's "Blocked by" to the blocking issues. Apply the `ready-for-agent` triage label unless instructed otherwise; the tickets are agent-grabbable by construction.
|
|
64
66
|
|
|
65
67
|
Work the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.
|