drawbore 0.1.0 → 0.1.1
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/CHANGELOG.md +28 -20
- package/LICENSE +20 -20
- package/README.md +75 -75
- package/bin/drawbore.js +334 -266
- package/lib/checker.js +398 -398
- package/lib/index.js +3 -1
- package/lib/installer.js +404 -404
- package/lib/prompts.js +375 -373
- package/package.json +42 -42
- package/skills/discover/SKILL.md +76 -76
- package/skills/frame/SKILL.md +84 -84
- package/skills/frame/references/change-brief.md +54 -54
- package/skills/init-project/SKILL.md +85 -85
- package/skills/recall/SKILL.md +61 -61
- package/skills/record/SKILL.md +98 -98
- package/skills/record/references/artifact-formats.md +130 -130
- package/skills/release/SKILL.md +107 -107
- package/skills/review/SKILL.md +116 -116
- package/templates/instruction.md +8 -8
- package/templates/manifest.json +11 -11
- package/templates/record/context.md +13 -13
- package/templates/record/glossary.md +6 -6
- package/templates/record/index.md +15 -15
- package/templates/record/principles.md +2 -2
- package/templates/record/stack.md +6 -6
- package/templates/record/system.md +2 -2
package/skills/review/SKILL.md
CHANGED
|
@@ -1,117 +1,117 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: review
|
|
3
|
-
description: Full read-only analysis of the working repository with a prioritized enhancement proposal, plus an approval-gated implementation phase — shape and stack, architecture and entry points, correctness and risk, hygiene and conventions, dependency and CI health, docs, and repository-specific convention drift. Use when asked to analyze, audit, review, assess, or improve a repo, codebase, or project, including "what should we improve", "review this project", "propose enhancements", "audit then fix", and post-change sanity audits. Analysis never edits; implementation runs only after explicit approval of a numbered plan.
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# Repository review (analysis + gated implementation)
|
|
7
|
-
|
|
8
|
-
Two phases. Phase 1 produces **one report** and never edits anything. Phase 2 runs only after the user approves specific numbered items, and only those.
|
|
9
|
-
|
|
10
|
-
## Rules
|
|
11
|
-
|
|
12
|
-
- **Evidence or nothing.** A finding without `path:line`, a file list, or a command's output is `[INFERENCE]` — it goes in the `Unverified` section, never in the ranked list.
|
|
13
|
-
- **Report what is there.** Missing files are findings only when a convention the repository itself declares requires them; do not grade the repo against an imagined ideal.
|
|
14
|
-
- **Read the repo's own checks before judging them.** Manifest scripts, `Makefile`, `justfile`, CI configuration, and lint rules are evidence of intent.
|
|
15
|
-
- **Rank, don't dump.** Order by `(impact × confidence) / effort`. A 30-item flat list is a failed audit.
|
|
16
|
-
- **Phase 1 ends at the report.** One question, at the end: what to implement.
|
|
17
|
-
- **Phase 2 is narrow.** Approved items only, in the approved order. No opportunistic cleanup, no adjacent refactor, no reformatting of touched files.
|
|
18
|
-
|
|
19
|
-
## Phase 1 — analysis
|
|
20
|
-
|
|
21
|
-
### 1. Shape
|
|
22
|
-
|
|
23
|
-
Confirm the workspace is the repository (resolve its root with the version-control tool the project uses), inspect working-tree state and recent history, and read the remotes. Then map it: read the root directory (one level), read the manifests (`package.json`, `Cargo.toml`, `pyproject.toml`, `*.csproj`, `go.mod`, `pom.xml`, …), and check for build, task-runner, and CI files. Note language, package manager, lockfile, entry points, test runner, linter, and CI provider. Record size per area with `find`/`xargs wc -l` when the tree is big enough to matter.
|
|
24
|
-
|
|
25
|
-
### 2. Architecture
|
|
26
|
-
|
|
27
|
-
Identify entry points and follow them: `main`/`index`/CLI parsers, HTTP handlers, exported public API. Then the dependency direction between modules — one `mermaid` block, only if there is genuine structure (layering, cross-cutting imports, a plugin boundary). Note cycles, layering violations, god files (> ~500 LOC), duplicated logic, and dead code. For dead code, use a language server's `references` on the symbol when one is configured; a text grep for a rename-class claim silently drops dynamic callsites.
|
|
28
|
-
|
|
29
|
-
### 3. Correctness and risk
|
|
30
|
-
|
|
31
|
-
Swallowed exceptions, empty `catch`, `any`/unchecked casts, and a `TODO`/`FIXME`/`HACK`/`XXX` inventory with locations. Unawaited promises, unlocked shared state, leaked handles, unvalidated input at trust boundaries. Then the things that page someone at 3am: missing timeouts, unbounded loops, unindexed queries, non-idempotent retries.
|
|
32
|
-
|
|
33
|
-
### 4. Hygiene and conventions
|
|
34
|
-
|
|
35
|
-
Tracked build output, secrets, `.env`, key material; ignore-file gaps; CRLF vs `.gitattributes`; inconsistent naming or formatting within one tree; stray debug logging; version stamps that disagree across files (manifest vs changelog vs header comments).
|
|
36
|
-
|
|
37
|
-
If the repository declares its own conventions (a root `AGENTS.md` or contributor guide, a documented release process, a required file layout), check the repository against them explicitly — that is the highest-yield pass. Compare declarations with reality and report every disagreement as a finding.
|
|
38
|
-
|
|
39
|
-
### 5. Dependencies and CI
|
|
40
|
-
|
|
41
|
-
Run the project's audit command (`npm audit`, `bun audit`, `cargo audit`, or the ecosystem equivalent; report advisories, never fix silently), note majors behind current, duplicated functionality across dependencies, dependencies never imported, and install scripts. For CI: read the pipeline definition, confirm every `needs`/stage edge is real, check that the pipeline runs on the branches and tags the project actually uses, and that the README badge URL matches the project path.
|
|
42
|
-
|
|
43
|
-
### 6. Security
|
|
44
|
-
|
|
45
|
-
If the harness exposes a security-scan or vulnerability-discovery tool, offer it as a **follow-up**, not a pass here — it has its own review flow and is opt-in. Run discovery, then validate each candidate before calling it real; report unvalidated candidates as leads. If no such tool is available, say so and list manual checks worth doing (dependency advisories, secret scanning, permission boundaries).
|
|
46
|
-
|
|
47
|
-
### 7. Docs
|
|
48
|
-
|
|
49
|
-
Does `README.md` answer what/why/install/use for a newcomer? Is `CHANGELOG.md` current against the latest tag? Does the contributor or agent guidance file match reality? License present and current-year?
|
|
50
|
-
|
|
51
|
-
### 8. Report
|
|
52
|
-
|
|
53
|
-
Lead with a 3–5 line verdict: what the repo is, its strongest and weakest aspect. Then, in order:
|
|
54
|
-
|
|
55
|
-
1. **Shape** — one paragraph, no restating the tree.
|
|
56
|
-
2. **Findings** — grouped by severity (`Blocker`, `Should fix`, `Nice to have`). Each carries a **stable id** (`F1`, `F2`, …), in this exact order: claim, evidence (`path:line` or command output), why it matters, concrete fix, effort (`S`/`M`/`L`).
|
|
57
|
-
3. **Comparison table** — id / finding / severity / area / effort / confidence.
|
|
58
|
-
4. **Proposed order of work** — 3–5 numbered steps referencing those ids, highest ratio first, each with a verifiable done-condition.
|
|
59
|
-
5. **Unverified** — `[INFERENCE]` items and what check would settle each.
|
|
60
|
-
|
|
61
|
-
End with exactly one question:
|
|
62
|
-
|
|
63
|
-
> Which items should I implement? Reply with ids or step numbers (e.g. `F1, F4` or `do step 2`). Anything not named stays untouched.
|
|
64
|
-
|
|
65
|
-
Then stop. Do not start implementing from a vague "yes" or "go ahead" — that authorizes nothing specific.
|
|
66
|
-
|
|
67
|
-
## Phase 2 — approval-gated implementation
|
|
68
|
-
|
|
69
|
-
Enter only on an explicit selection of ids or step numbers.
|
|
70
|
-
|
|
71
|
-
### 2.1 Confirm the scope, in writing
|
|
72
|
-
|
|
73
|
-
Before the first edit, restate the selected ids with: files each will touch, the change in one line, the done-condition, and the verification command. Then require an explicit confirmation naming that scope. A single "yes" to the phase-1 question is not this confirmation.
|
|
74
|
-
|
|
75
|
-
### 2.2 Baseline first
|
|
76
|
-
|
|
77
|
-
Run the verification command **before** editing, and record the output. A verification step is worthless if it was already failing, and a red baseline tells you the repo was broken before you arrived — report that rather than attributing it to your change.
|
|
78
|
-
|
|
79
|
-
### 2.3 Implement in plan order
|
|
80
|
-
|
|
81
|
-
One id at a time, in the approved order. Each item:
|
|
82
|
-
|
|
83
|
-
1. Read the target code; check references for any exported symbol before renaming.
|
|
84
|
-
2. Make the change.
|
|
85
|
-
3. Run the done-condition check.
|
|
86
|
-
4. Report `id — done | failed: <output>`. Then next id.
|
|
87
|
-
|
|
88
|
-
If an item turns out to be wrong, larger than stated, or to require touching files outside its declared scope: **stop, report, ask.** Do not widen the change to keep momentum.
|
|
89
|
-
|
|
90
|
-
### 2.4 Final verification
|
|
91
|
-
|
|
92
|
-
Re-run the repository's own checks once, after all items: build, tests, lint. Fix only failures your changes caused — a pre-existing failure goes in the report, not into a drive-by fix.
|
|
93
|
-
|
|
94
|
-
### 2.5 Close out
|
|
95
|
-
|
|
96
|
-
Report what changed (id → file → what), what verification proved, and what was left undone. Update docs or changelog if the change is user-visible.
|
|
97
|
-
|
|
98
|
-
## Boundaries that never move
|
|
99
|
-
|
|
100
|
-
- **No commits, no pushes, no tags, no version bumps** in either phase unless the user explicitly asks for that step. Phase 2 authorizes edits only.
|
|
101
|
-
- **No dependency changes** unless the user named the item as a dependency change.
|
|
102
|
-
- **No touching unrelated code**, however tempting. "I fixed a typo nearby" turns an approved change into an unapproved diff.
|
|
103
|
-
- **Nothing outside the repository** unless the user explicitly authorizes it: harness configuration, global tool configuration, system installs.
|
|
104
|
-
- **Items the user did not select are not implemented.** Not partially, not "while I was there".
|
|
105
|
-
|
|
106
|
-
## Large repositories
|
|
107
|
-
|
|
108
|
-
If the harness offers session checkpoints or a rewind mechanism, snapshot before exploration and keep only the report. Delegate independent areas (build, tests, dependencies, CI, docs) as parallel read-only subagents in one dispatch when a single pass would be shallow; per-area finders return evidence, not prose. You keep the synthesis, the prioritization, and phase 2.
|
|
109
|
-
|
|
110
|
-
## Anti-patterns
|
|
111
|
-
|
|
112
|
-
- Formatting nits as findings. Mention once, in aggregate.
|
|
113
|
-
- Proposing a framework or rewrite without naming what it buys over the current design.
|
|
114
|
-
- Findings the repo already documents as intentional (search the docs first).
|
|
115
|
-
- Running builds or test suites during phase 1 unless a finding requires it; an audit observes, it does not verify work.
|
|
116
|
-
- Editing anything in phase 1. The moment you fix a typo, it is not an audit.
|
|
1
|
+
---
|
|
2
|
+
name: review
|
|
3
|
+
description: Full read-only analysis of the working repository with a prioritized enhancement proposal, plus an approval-gated implementation phase — shape and stack, architecture and entry points, correctness and risk, hygiene and conventions, dependency and CI health, docs, and repository-specific convention drift. Use when asked to analyze, audit, review, assess, or improve a repo, codebase, or project, including "what should we improve", "review this project", "propose enhancements", "audit then fix", and post-change sanity audits. Analysis never edits; implementation runs only after explicit approval of a numbered plan.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Repository review (analysis + gated implementation)
|
|
7
|
+
|
|
8
|
+
Two phases. Phase 1 produces **one report** and never edits anything. Phase 2 runs only after the user approves specific numbered items, and only those.
|
|
9
|
+
|
|
10
|
+
## Rules
|
|
11
|
+
|
|
12
|
+
- **Evidence or nothing.** A finding without `path:line`, a file list, or a command's output is `[INFERENCE]` — it goes in the `Unverified` section, never in the ranked list.
|
|
13
|
+
- **Report what is there.** Missing files are findings only when a convention the repository itself declares requires them; do not grade the repo against an imagined ideal.
|
|
14
|
+
- **Read the repo's own checks before judging them.** Manifest scripts, `Makefile`, `justfile`, CI configuration, and lint rules are evidence of intent.
|
|
15
|
+
- **Rank, don't dump.** Order by `(impact × confidence) / effort`. A 30-item flat list is a failed audit.
|
|
16
|
+
- **Phase 1 ends at the report.** One question, at the end: what to implement.
|
|
17
|
+
- **Phase 2 is narrow.** Approved items only, in the approved order. No opportunistic cleanup, no adjacent refactor, no reformatting of touched files.
|
|
18
|
+
|
|
19
|
+
## Phase 1 — analysis
|
|
20
|
+
|
|
21
|
+
### 1. Shape
|
|
22
|
+
|
|
23
|
+
Confirm the workspace is the repository (resolve its root with the version-control tool the project uses), inspect working-tree state and recent history, and read the remotes. Then map it: read the root directory (one level), read the manifests (`package.json`, `Cargo.toml`, `pyproject.toml`, `*.csproj`, `go.mod`, `pom.xml`, …), and check for build, task-runner, and CI files. Note language, package manager, lockfile, entry points, test runner, linter, and CI provider. Record size per area with `find`/`xargs wc -l` when the tree is big enough to matter.
|
|
24
|
+
|
|
25
|
+
### 2. Architecture
|
|
26
|
+
|
|
27
|
+
Identify entry points and follow them: `main`/`index`/CLI parsers, HTTP handlers, exported public API. Then the dependency direction between modules — one `mermaid` block, only if there is genuine structure (layering, cross-cutting imports, a plugin boundary). Note cycles, layering violations, god files (> ~500 LOC), duplicated logic, and dead code. For dead code, use a language server's `references` on the symbol when one is configured; a text grep for a rename-class claim silently drops dynamic callsites.
|
|
28
|
+
|
|
29
|
+
### 3. Correctness and risk
|
|
30
|
+
|
|
31
|
+
Swallowed exceptions, empty `catch`, `any`/unchecked casts, and a `TODO`/`FIXME`/`HACK`/`XXX` inventory with locations. Unawaited promises, unlocked shared state, leaked handles, unvalidated input at trust boundaries. Then the things that page someone at 3am: missing timeouts, unbounded loops, unindexed queries, non-idempotent retries.
|
|
32
|
+
|
|
33
|
+
### 4. Hygiene and conventions
|
|
34
|
+
|
|
35
|
+
Tracked build output, secrets, `.env`, key material; ignore-file gaps; CRLF vs `.gitattributes`; inconsistent naming or formatting within one tree; stray debug logging; version stamps that disagree across files (manifest vs changelog vs header comments).
|
|
36
|
+
|
|
37
|
+
If the repository declares its own conventions (a root `AGENTS.md` or contributor guide, a documented release process, a required file layout), check the repository against them explicitly — that is the highest-yield pass. Compare declarations with reality and report every disagreement as a finding.
|
|
38
|
+
|
|
39
|
+
### 5. Dependencies and CI
|
|
40
|
+
|
|
41
|
+
Run the project's audit command (`npm audit`, `bun audit`, `cargo audit`, or the ecosystem equivalent; report advisories, never fix silently), note majors behind current, duplicated functionality across dependencies, dependencies never imported, and install scripts. For CI: read the pipeline definition, confirm every `needs`/stage edge is real, check that the pipeline runs on the branches and tags the project actually uses, and that the README badge URL matches the project path.
|
|
42
|
+
|
|
43
|
+
### 6. Security
|
|
44
|
+
|
|
45
|
+
If the harness exposes a security-scan or vulnerability-discovery tool, offer it as a **follow-up**, not a pass here — it has its own review flow and is opt-in. Run discovery, then validate each candidate before calling it real; report unvalidated candidates as leads. If no such tool is available, say so and list manual checks worth doing (dependency advisories, secret scanning, permission boundaries).
|
|
46
|
+
|
|
47
|
+
### 7. Docs
|
|
48
|
+
|
|
49
|
+
Does `README.md` answer what/why/install/use for a newcomer? Is `CHANGELOG.md` current against the latest tag? Does the contributor or agent guidance file match reality? License present and current-year?
|
|
50
|
+
|
|
51
|
+
### 8. Report
|
|
52
|
+
|
|
53
|
+
Lead with a 3–5 line verdict: what the repo is, its strongest and weakest aspect. Then, in order:
|
|
54
|
+
|
|
55
|
+
1. **Shape** — one paragraph, no restating the tree.
|
|
56
|
+
2. **Findings** — grouped by severity (`Blocker`, `Should fix`, `Nice to have`). Each carries a **stable id** (`F1`, `F2`, …), in this exact order: claim, evidence (`path:line` or command output), why it matters, concrete fix, effort (`S`/`M`/`L`).
|
|
57
|
+
3. **Comparison table** — id / finding / severity / area / effort / confidence.
|
|
58
|
+
4. **Proposed order of work** — 3–5 numbered steps referencing those ids, highest ratio first, each with a verifiable done-condition.
|
|
59
|
+
5. **Unverified** — `[INFERENCE]` items and what check would settle each.
|
|
60
|
+
|
|
61
|
+
End with exactly one question:
|
|
62
|
+
|
|
63
|
+
> Which items should I implement? Reply with ids or step numbers (e.g. `F1, F4` or `do step 2`). Anything not named stays untouched.
|
|
64
|
+
|
|
65
|
+
Then stop. Do not start implementing from a vague "yes" or "go ahead" — that authorizes nothing specific.
|
|
66
|
+
|
|
67
|
+
## Phase 2 — approval-gated implementation
|
|
68
|
+
|
|
69
|
+
Enter only on an explicit selection of ids or step numbers.
|
|
70
|
+
|
|
71
|
+
### 2.1 Confirm the scope, in writing
|
|
72
|
+
|
|
73
|
+
Before the first edit, restate the selected ids with: files each will touch, the change in one line, the done-condition, and the verification command. Then require an explicit confirmation naming that scope. A single "yes" to the phase-1 question is not this confirmation.
|
|
74
|
+
|
|
75
|
+
### 2.2 Baseline first
|
|
76
|
+
|
|
77
|
+
Run the verification command **before** editing, and record the output. A verification step is worthless if it was already failing, and a red baseline tells you the repo was broken before you arrived — report that rather than attributing it to your change.
|
|
78
|
+
|
|
79
|
+
### 2.3 Implement in plan order
|
|
80
|
+
|
|
81
|
+
One id at a time, in the approved order. Each item:
|
|
82
|
+
|
|
83
|
+
1. Read the target code; check references for any exported symbol before renaming.
|
|
84
|
+
2. Make the change.
|
|
85
|
+
3. Run the done-condition check.
|
|
86
|
+
4. Report `id — done | failed: <output>`. Then next id.
|
|
87
|
+
|
|
88
|
+
If an item turns out to be wrong, larger than stated, or to require touching files outside its declared scope: **stop, report, ask.** Do not widen the change to keep momentum.
|
|
89
|
+
|
|
90
|
+
### 2.4 Final verification
|
|
91
|
+
|
|
92
|
+
Re-run the repository's own checks once, after all items: build, tests, lint. Fix only failures your changes caused — a pre-existing failure goes in the report, not into a drive-by fix.
|
|
93
|
+
|
|
94
|
+
### 2.5 Close out
|
|
95
|
+
|
|
96
|
+
Report what changed (id → file → what), what verification proved, and what was left undone. Update docs or changelog if the change is user-visible.
|
|
97
|
+
|
|
98
|
+
## Boundaries that never move
|
|
99
|
+
|
|
100
|
+
- **No commits, no pushes, no tags, no version bumps** in either phase unless the user explicitly asks for that step. Phase 2 authorizes edits only.
|
|
101
|
+
- **No dependency changes** unless the user named the item as a dependency change.
|
|
102
|
+
- **No touching unrelated code**, however tempting. "I fixed a typo nearby" turns an approved change into an unapproved diff.
|
|
103
|
+
- **Nothing outside the repository** unless the user explicitly authorizes it: harness configuration, global tool configuration, system installs.
|
|
104
|
+
- **Items the user did not select are not implemented.** Not partially, not "while I was there".
|
|
105
|
+
|
|
106
|
+
## Large repositories
|
|
107
|
+
|
|
108
|
+
If the harness offers session checkpoints or a rewind mechanism, snapshot before exploration and keep only the report. Delegate independent areas (build, tests, dependencies, CI, docs) as parallel read-only subagents in one dispatch when a single pass would be shallow; per-area finders return evidence, not prose. You keep the synthesis, the prioritization, and phase 2.
|
|
109
|
+
|
|
110
|
+
## Anti-patterns
|
|
111
|
+
|
|
112
|
+
- Formatting nits as findings. Mention once, in aggregate.
|
|
113
|
+
- Proposing a framework or rewrite without naming what it buys over the current design.
|
|
114
|
+
- Findings the repo already documents as intentional (search the docs first).
|
|
115
|
+
- Running builds or test suites during phase 1 unless a finding requires it; an audit observes, it does not verify work.
|
|
116
|
+
- Editing anything in phase 1. The moment you fix a typo, it is not an audit.
|
|
117
117
|
- Treating "yes, implement" as approval for all findings. It is approval for the ones you listed.
|
package/templates/instruction.md
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
|
-
<!-- drawbore:start -->
|
|
2
|
-
## Drawbore
|
|
3
|
-
|
|
4
|
-
This project uses `.drawbore/` as its curated, durable project context. Drawbore installs portable skills into the agent harness; use the `discover`, `recall`, `frame`, `record`, `review`, `init-project`, and `release` skills where the task calls for them.
|
|
5
|
-
|
|
6
|
-
Before implementing a feature, bug fix, refactor, design change, or other technical change, consult the relevant project context, glossary and canonical terms, principles, decisions, current behavior, technical choices, and active Change Briefs. If purpose, scope, or a boundary is materially ambiguous, or the request conflicts with a recorded principle, decision, term, or boundary, collaborate with the developer to resolve it before implementation.
|
|
7
|
-
|
|
8
|
-
After completing work, reconcile the implementation and verified behavior with durable project context. Offer specific evidence-backed updates and wait for explicit **apply** or approval of edited wording; **skip** or no decision leaves the record unchanged. If no durable consequence changed, explicitly state **No record update needed**. Never silently change curated project truth.
|
|
1
|
+
<!-- drawbore:start -->
|
|
2
|
+
## Drawbore
|
|
3
|
+
|
|
4
|
+
This project uses `.drawbore/` as its curated, durable project context. Drawbore installs portable skills into the agent harness; use the `discover`, `recall`, `frame`, `record`, `review`, `init-project`, and `release` skills where the task calls for them.
|
|
5
|
+
|
|
6
|
+
Before implementing a feature, bug fix, refactor, design change, or other technical change, consult the relevant project context, glossary and canonical terms, principles, decisions, current behavior, technical choices, and active Change Briefs. If purpose, scope, or a boundary is materially ambiguous, or the request conflicts with a recorded principle, decision, term, or boundary, collaborate with the developer to resolve it before implementation.
|
|
7
|
+
|
|
8
|
+
After completing work, reconcile the implementation and verified behavior with durable project context. Offer specific evidence-backed updates and wait for explicit **apply** or approval of edited wording; **skip** or no decision leaves the record unchanged. If no durable consequence changed, explicitly state **No record update needed**. Never silently change curated project truth.
|
|
9
9
|
<!-- drawbore:end -->
|
package/templates/manifest.json
CHANGED
|
@@ -1,12 +1,12 @@
|
|
|
1
|
-
{
|
|
2
|
-
"namespace": "drawbore",
|
|
3
|
-
"skills": [
|
|
4
|
-
"discover",
|
|
5
|
-
"recall",
|
|
6
|
-
"frame",
|
|
7
|
-
"record",
|
|
8
|
-
"review",
|
|
9
|
-
"init-project",
|
|
10
|
-
"release"
|
|
11
|
-
]
|
|
1
|
+
{
|
|
2
|
+
"namespace": "drawbore",
|
|
3
|
+
"skills": [
|
|
4
|
+
"discover",
|
|
5
|
+
"recall",
|
|
6
|
+
"frame",
|
|
7
|
+
"record",
|
|
8
|
+
"review",
|
|
9
|
+
"init-project",
|
|
10
|
+
"release"
|
|
11
|
+
]
|
|
12
12
|
}
|
|
@@ -1,14 +1,14 @@
|
|
|
1
|
-
# Project Context
|
|
2
|
-
|
|
3
|
-
## Purpose
|
|
4
|
-
|
|
5
|
-
<!-- Why this project exists and the outcome it serves. -->
|
|
6
|
-
|
|
7
|
-
## Scope
|
|
8
|
-
|
|
9
|
-
- <!-- Included boundary. -->
|
|
10
|
-
- <!-- Excluded boundary. -->
|
|
11
|
-
|
|
12
|
-
## Architecture and relationships
|
|
13
|
-
|
|
1
|
+
# Project Context
|
|
2
|
+
|
|
3
|
+
## Purpose
|
|
4
|
+
|
|
5
|
+
<!-- Why this project exists and the outcome it serves. -->
|
|
6
|
+
|
|
7
|
+
## Scope
|
|
8
|
+
|
|
9
|
+
- <!-- Included boundary. -->
|
|
10
|
+
- <!-- Excluded boundary. -->
|
|
11
|
+
|
|
12
|
+
## Architecture and relationships
|
|
13
|
+
|
|
14
14
|
- **<!-- Area or component -->** — <!-- Responsibility and relationship to other areas. -->
|
|
@@ -1,7 +1,7 @@
|
|
|
1
|
-
# Glossary
|
|
2
|
-
|
|
3
|
-
## <!-- Context or area -->
|
|
4
|
-
|
|
5
|
-
**<!-- Canonical term -->**:
|
|
6
|
-
<!-- One or two-sentence definition. -->
|
|
1
|
+
# Glossary
|
|
2
|
+
|
|
3
|
+
## <!-- Context or area -->
|
|
4
|
+
|
|
5
|
+
**<!-- Canonical term -->**:
|
|
6
|
+
<!-- One or two-sentence definition. -->
|
|
7
7
|
_Avoid_: <!-- Discouraged alias or alternative name. -->
|
|
@@ -1,16 +1,16 @@
|
|
|
1
|
-
# Project Notebook
|
|
2
|
-
|
|
3
|
-
Durable, curated context for this project.
|
|
4
|
-
|
|
5
|
-
## Durable context
|
|
6
|
-
|
|
7
|
-
- [Context](context.md) — purpose, scope, architecture, and relationships.
|
|
8
|
-
- [Glossary](glossary.md) — canonical terms and discouraged aliases.
|
|
9
|
-
- [Principles](principles.md) — rules that constrain future work.
|
|
10
|
-
- [Decisions](decisions/) — durable choices and their rationale.
|
|
11
|
-
- [System behavior](system.md) — current shipped capabilities and contracts.
|
|
12
|
-
- [Technical choices](stack.md) — current stack and architecture.
|
|
13
|
-
|
|
14
|
-
## Transient work
|
|
15
|
-
|
|
1
|
+
# Project Notebook
|
|
2
|
+
|
|
3
|
+
Durable, curated context for this project.
|
|
4
|
+
|
|
5
|
+
## Durable context
|
|
6
|
+
|
|
7
|
+
- [Context](context.md) — purpose, scope, architecture, and relationships.
|
|
8
|
+
- [Glossary](glossary.md) — canonical terms and discouraged aliases.
|
|
9
|
+
- [Principles](principles.md) — rules that constrain future work.
|
|
10
|
+
- [Decisions](decisions/) — durable choices and their rationale.
|
|
11
|
+
- [System behavior](system.md) — current shipped capabilities and contracts.
|
|
12
|
+
- [Technical choices](stack.md) — current stack and architecture.
|
|
13
|
+
|
|
14
|
+
## Transient work
|
|
15
|
+
|
|
16
16
|
- [Change Briefs](work/) — scope being shaped or implemented. Promote durable consequences and remove settled briefs.
|
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
# Principles
|
|
2
|
-
|
|
1
|
+
# Principles
|
|
2
|
+
|
|
3
3
|
<!-- Load-bearing rules only. Include rationale and provenance. -->
|
|
@@ -1,7 +1,7 @@
|
|
|
1
|
-
# Technical Choices
|
|
2
|
-
|
|
3
|
-
<!-- Current project-specific choices and architecture. -->
|
|
4
|
-
|
|
5
|
-
## Architecture
|
|
6
|
-
|
|
1
|
+
# Technical Choices
|
|
2
|
+
|
|
3
|
+
<!-- Current project-specific choices and architecture. -->
|
|
4
|
+
|
|
5
|
+
## Architecture
|
|
6
|
+
|
|
7
7
|
- <!-- Component, boundary, or relationship. -->
|
|
@@ -1,3 +1,3 @@
|
|
|
1
|
-
# System Behavior
|
|
2
|
-
|
|
1
|
+
# System Behavior
|
|
2
|
+
|
|
3
3
|
<!-- Current shipped capabilities and contracts only. -->
|