@archme/cli 0.9.1 → 0.10.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/SKILL.md +38 -0
- package/dist/cli.js +3191 -474
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -98,6 +98,44 @@ consumers filter on them.
|
|
|
98
98
|
8. Submit stories, connections, requirements as usual.
|
|
99
99
|
```
|
|
100
100
|
|
|
101
|
+
### Workflow: multi-repo bootstrap
|
|
102
|
+
|
|
103
|
+
One project, one graph, each repo a root-level `kind: "repo"` container.
|
|
104
|
+
One command, run from the folder holding the clones (or where they should go):
|
|
105
|
+
|
|
106
|
+
```
|
|
107
|
+
archme add-repos [clone-path | owner/name …] --project <org/slug> [--local] [--parallel <n>] [--yes]
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
An `owner/name` uses a clone of that repo already in the current folder, or is
|
|
111
|
+
cloned there with the user's own git access. With no repos given, every clone
|
|
112
|
+
directly under the current folder is added.
|
|
113
|
+
|
|
114
|
+
1. **Checks** the project, the GitHub App for each new repo (unless `--local`)
|
|
115
|
+
and every container before writing anything; folds a single-repo board into
|
|
116
|
+
its repo's container first.
|
|
117
|
+
2. **Plan session** (interactive): creates every container and the shared
|
|
118
|
+
externals, records the conventions in root context, and drafts the story
|
|
119
|
+
plan — draft leaves naming the repos they touch — with the user. On exit
|
|
120
|
+
the CLI asks whether to scan against it; declining can restore the board.
|
|
121
|
+
3. **One headless scan per repo**, inside its own clone, up to `--parallel`
|
|
122
|
+
(default 2, max 3) at once: watch with its container, scan into that
|
|
123
|
+
container with repo-relative anchors against the plan, `complete_scan`.
|
|
124
|
+
Departures from the plan go in root context as
|
|
125
|
+
`multi-repo-plan-changes-<container>`.
|
|
126
|
+
4. **Stitch session** (interactive): wires cross-repo connections and
|
|
127
|
+
stories, finishes the plan's cross-repo stories, and writes
|
|
128
|
+
`multi-repo-plan-changes` — what changed from the approved plan, and why.
|
|
129
|
+
|
|
130
|
+
Re-running skips repos already watched with a marker and a populated
|
|
131
|
+
container, so a failed run resumes. `--yes` runs everything headless and
|
|
132
|
+
approves the plan. The steps also run alone: `archme scan --roster`,
|
|
133
|
+
`archme add-repo` (one clone), `archme scan --stitch`.
|
|
134
|
+
|
|
135
|
+
On a multi-repo project, read `read_context({ path: "root", type: "decision" })`
|
|
136
|
+
before modelling anything that crosses repos, and never create a root-level
|
|
137
|
+
external for a system that is a repo container — `update_architecture` rejects it.
|
|
138
|
+
|
|
101
139
|
### Story granularity
|
|
102
140
|
|
|
103
141
|
Before you mint a user story, decide it deserves to be one. A story should be
|