reins-method 0.1.1 → 0.1.2
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 +22 -27
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -81,13 +81,9 @@ global install covers every project on the machine, in every supported agent.
|
|
|
81
81
|
|
|
82
82
|
### Why does the installer need Node, if REINS is a bash CLI?
|
|
83
83
|
|
|
84
|
-
Only the *installer* (`npx reins-method install`) uses Node
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
`npx bmad-method install`. It collects your answers, then hands them to `bin/reins
|
|
88
|
-
install --non-interactive` to do the actual file work. Everything you run
|
|
89
|
-
afterwards — `reins update`, `reins sync`, `reins new-adapter`, etc. — is plain
|
|
90
|
-
bash with no runtime dependencies. If you'd rather not use Node at all, `install.sh`
|
|
84
|
+
Only the *installer* (`npx reins-method install`) uses Node, for the arrow-key
|
|
85
|
+
menus. Everything you run afterwards — `reins update`, `reins sync`, `reins
|
|
86
|
+
new-adapter`, etc. — is plain bash with no runtime dependencies. No Node? `install.sh`
|
|
91
87
|
runs the same wizard with `read -p` prompts instead of menus.
|
|
92
88
|
|
|
93
89
|
---
|
|
@@ -171,26 +167,25 @@ or invoke `skill-creator` for guided creation. See [SKILLS.md](SKILLS.md).
|
|
|
171
167
|
## Personas, Party Mode & Code Review
|
|
172
168
|
|
|
173
169
|
Six built-in persona skills give you BMAD-style perspectives natively, with no
|
|
174
|
-
external install
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
| `reins-
|
|
180
|
-
| `reins-
|
|
181
|
-
| `reins-
|
|
182
|
-
| `reins-
|
|
183
|
-
| `reins-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
with a plain-language summary of what needs fixing before merge.
|
|
170
|
+
external install:
|
|
171
|
+
|
|
172
|
+
| Skill | Lens |
|
|
173
|
+
|---|---|
|
|
174
|
+
| `reins-business-analyst` | Methodical, evidence-based (Porter, Minto Pyramid), represents every stakeholder — including the inconvenient ones — never takes sides |
|
|
175
|
+
| `reins-technical-writer` | CommonMark/DITA/OpenAPI, writes for the reader with zero context, diagrams over walls of text |
|
|
176
|
+
| `reins-product-manager` | Jobs-to-be-Done, pragmatic and people-focused, skeptical of complexity that doesn't earn its cost |
|
|
177
|
+
| `reins-ux-designer` | Deeply empathetic, thinks in user flows and friction points, every decision serves a genuine user need |
|
|
178
|
+
| `reins-system-architect` | Calm and strategic, favors proven tech, developer productivity, ties decisions to business value |
|
|
179
|
+
| `reins-senior-engineer` | Test-first (red/green/refactor), 100% passing before review, no shortcuts |
|
|
180
|
+
|
|
181
|
+
Each is callable individually (e.g. "give me the system architect's take on
|
|
182
|
+
this"). Before a breakdown, ask for **`party-mode`** — a facilitator picks the
|
|
183
|
+
relevant personas (always the business analyst) and announces the lineup, each
|
|
184
|
+
speaks in turn, then a synthesizer distills it into what matters for the
|
|
185
|
+
breakdown. Before proposing a commit message, ask for **`code-review`** — it
|
|
186
|
+
launches independent subagents (logic, security, and requirements if a SPEC
|
|
187
|
+
exists) for adversarial, parallel review, then closes with a plain-language
|
|
188
|
+
summary of what needs fixing before merge.
|
|
194
189
|
|
|
195
190
|
---
|
|
196
191
|
|
package/package.json
CHANGED