@tduyng/pi-devos 0.0.0-stage → 0.14.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.
Files changed (109) hide show
  1. package/CHANGELOG.md +1421 -0
  2. package/LICENSE +201 -0
  3. package/README.md +206 -2
  4. package/package.json +44 -4
  5. package/plugins/devos/agents/reader.md +27 -0
  6. package/plugins/devos/agents/verifier.md +155 -0
  7. package/plugins/devos/pi/extension/devos.ts +605 -0
  8. package/plugins/devos/scripts/check-evidence-router.sh +140 -0
  9. package/plugins/devos/scripts/evidence-router.py +254 -0
  10. package/plugins/devos/scripts/gates/check-dod-core.sh +285 -0
  11. package/plugins/devos/scripts/gates/check-dod.sh +38 -0
  12. package/plugins/devos/scripts/gates/check-implementation-boundary.sh +99 -0
  13. package/plugins/devos/scripts/gates/check-port-source.sh +134 -0
  14. package/plugins/devos/scripts/gates/check-report-locations.sh +148 -0
  15. package/plugins/devos/scripts/gates/check-scenario-coverage.sh +104 -0
  16. package/plugins/devos/scripts/gates/gate-check.mjs +204 -0
  17. package/plugins/devos/scripts/gates/phase-gate.sh +208 -0
  18. package/plugins/devos/scripts/gates/plan-template-check.py +141 -0
  19. package/plugins/devos/scripts/gates/run-gate.sh +148 -0
  20. package/plugins/devos/scripts/gates/spec-contract.sh +19 -0
  21. package/plugins/devos/scripts/gates/spec-template-check.py +152 -0
  22. package/plugins/devos/scripts/gates/suite/01-dod.sh +485 -0
  23. package/plugins/devos/scripts/gates/suite/02-integrity.sh +310 -0
  24. package/plugins/devos/scripts/gates/suite/03-archetype.sh +255 -0
  25. package/plugins/devos/scripts/gates/suite/04-spec-validator.sh +183 -0
  26. package/plugins/devos/scripts/gates/suite/05-requires.sh +360 -0
  27. package/plugins/devos/scripts/gates/suite/06-clarify-adapters.sh +435 -0
  28. package/plugins/devos/scripts/gates/suite/07-lint-evals.sh +350 -0
  29. package/plugins/devos/scripts/gates/suite/08-converge.sh +591 -0
  30. package/plugins/devos/scripts/gates/suite/09-quality.sh +516 -0
  31. package/plugins/devos/scripts/gates/suite/10-eval-harness.sh +679 -0
  32. package/plugins/devos/scripts/gates/test-gates.sh +76 -0
  33. package/plugins/devos/scripts/gates/test-integrity-rubric.sh +152 -0
  34. package/plugins/devos/scripts/gates/test-phase-gate.sh +116 -0
  35. package/plugins/devos/skills/absorb/SKILL.md +75 -0
  36. package/plugins/devos/skills/absorb/references/distill.md +67 -0
  37. package/plugins/devos/skills/absorb/scripts/check-refs.sh +108 -0
  38. package/plugins/devos/skills/absorb/scripts/knowledge.py +258 -0
  39. package/plugins/devos/skills/build/SKILL.md +71 -0
  40. package/plugins/devos/skills/build/references/advanced-routing.md +19 -0
  41. package/plugins/devos/skills/build/references/defect.md +17 -0
  42. package/plugins/devos/skills/build/references/exposure.md +28 -0
  43. package/plugins/devos/skills/build/references/hard.md +39 -0
  44. package/plugins/devos/skills/build/references/refactor.md +66 -0
  45. package/plugins/devos/skills/build/references/routes.md +56 -0
  46. package/plugins/devos/skills/build/references/scale.md +84 -0
  47. package/plugins/devos/skills/build/references/spike.md +19 -0
  48. package/plugins/devos/skills/build/scripts/construct-census.py +204 -0
  49. package/plugins/devos/skills/build/scripts/dep-order.py +297 -0
  50. package/plugins/devos/skills/build/scripts/ledger.sh +228 -0
  51. package/plugins/devos/skills/build/scripts/route.sh +5 -0
  52. package/plugins/devos/skills/build/scripts/secret-scan.sh +121 -0
  53. package/plugins/devos/skills/build/scripts/toolchain-preflight.py +302 -0
  54. package/plugins/devos/skills/frame/SKILL.md +54 -0
  55. package/plugins/devos/skills/frame/references/template.md +115 -0
  56. package/plugins/devos/skills/frame/scripts/survey.sh +44 -0
  57. package/plugins/devos/skills/implement/SKILL.md +36 -0
  58. package/plugins/devos/skills/implement/references/conditional-plan.md +17 -0
  59. package/plugins/devos/skills/implement/references/debug-loop.md +7 -0
  60. package/plugins/devos/skills/implement/references/dod.md +37 -0
  61. package/plugins/devos/skills/implement/references/implement.md +54 -0
  62. package/plugins/devos/skills/implement/references/manual-gates.md +16 -0
  63. package/plugins/devos/skills/implement/references/plan.md +142 -0
  64. package/plugins/devos/skills/implement/references/resume.md +9 -0
  65. package/plugins/devos/skills/implement/references/scale.md +86 -0
  66. package/plugins/devos/skills/implement/references/verify-close.md +62 -0
  67. package/plugins/devos/skills/implement/references/visual-verification.md +7 -0
  68. package/plugins/devos/skills/implement/scripts/check-converge.sh +147 -0
  69. package/plugins/devos/skills/implement/scripts/equivalence-check.sh +140 -0
  70. package/plugins/devos/skills/implement/scripts/manifest-queue.sh +185 -0
  71. package/plugins/devos/skills/implement/scripts/ops-log.sh +58 -0
  72. package/plugins/devos/skills/implement/scripts/pilot-consistency.py +173 -0
  73. package/plugins/devos/skills/implement/scripts/validate-spec.sh +220 -0
  74. package/plugins/devos/skills/init/SKILL.md +100 -0
  75. package/plugins/devos/skills/init/references/archetype-sections.md +15 -0
  76. package/plugins/devos/skills/init/references/context.md +42 -0
  77. package/plugins/devos/skills/init/references/conventions-template.md +153 -0
  78. package/plugins/devos/skills/init/references/reverse-engineer.md +3 -0
  79. package/plugins/devos/skills/init/references/rule-format.md +58 -0
  80. package/plugins/devos/skills/init/references/shape-model.md +29 -0
  81. package/plugins/devos/skills/init/scripts/detect-archetype.py +461 -0
  82. package/plugins/devos/skills/init/scripts/render-rule.py +114 -0
  83. package/plugins/devos/skills/init/scripts/reverse-engineer.sh +162 -0
  84. package/plugins/devos/skills/learn/SKILL.md +29 -0
  85. package/plugins/devos/skills/learn/references/destinations.md +43 -0
  86. package/plugins/devos/skills/learn/references/scoring.md +26 -0
  87. package/plugins/devos/skills/review/SKILL.md +54 -0
  88. package/plugins/devos/skills/review/references/comments.md +13 -0
  89. package/plugins/devos/skills/review/references/gaps.md +26 -0
  90. package/plugins/devos/skills/review/references/reviewer.md +124 -0
  91. package/plugins/devos/skills/review/references/routing.md +35 -0
  92. package/plugins/devos/skills/review/scripts/__pycache__/prepare.cpython-313.pyc +0 -0
  93. package/plugins/devos/skills/review/scripts/prepare.py +763 -0
  94. package/plugins/devos/skills/spec/SKILL.md +57 -0
  95. package/plugins/devos/skills/spec/references/prototype.md +21 -0
  96. package/plugins/devos/skills/spec/references/question-craft.md +47 -0
  97. package/plugins/devos/skills/spec/references/roadmap-link.md +5 -0
  98. package/plugins/devos/skills/spec/references/write-spec.md +128 -0
  99. package/plugins/devos/skills/spec/scripts/clarify.sh +173 -0
  100. package/plugins/devos/skills/status/SKILL.md +67 -0
  101. package/plugins/devos/skills/status/references/cost.md +38 -0
  102. package/plugins/devos/skills/status/scripts/artifact-budgets.sh +88 -0
  103. package/plugins/devos/skills/status/scripts/check-requires.py +556 -0
  104. package/plugins/devos/skills/status/scripts/context-cost.sh +89 -0
  105. package/plugins/devos/skills/status/scripts/convention-usage.sh +184 -0
  106. package/plugins/devos/skills/status/scripts/findings-summary.sh +112 -0
  107. package/plugins/devos/skills/status/scripts/quality-correlation.sh +259 -0
  108. package/plugins/devos/skills/status/scripts/sizing-calibration.sh +71 -0
  109. package/plugins/devos/skills/status/scripts/spec-diff.sh +137 -0
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 tduyng
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md CHANGED
@@ -1,3 +1,207 @@
1
- # Temporary Holding Version
1
+ # DevOS
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ DevOS is a lazy SDD framework for one engineer or a small team. It keeps the process proportional to the task and makes the agent prove its work before calling it done.
4
+
5
+ You should not have to remember any of it. You type one thing, what you want changed, and DevOS decides what that needs: the route, the questions worth asking, the plan, the checks. It names the route before it starts, and the only thing it asks of you is a yes or an answer. A typo fix gets no ceremony. A new feature gets a short spec you approve before any code is written.
6
+
7
+ Works with Pi, Claude Code, Cursor, Copilot, Codex, and OpenCode. You do not need to know anything about spec-driven development to use it.
8
+
9
+ The Pi package is named `@tduyng/pi-devos`: `pi` names the tool it plugs into, `devos` the framework. OpenCode follows the same pattern with `opencode-devos`, and Claude Code, Codex and Copilot install a plugin named `devos`. The skills, the gates and the lifecycle are the same on every tool. If you installed `pi-devos`, you have DevOS for Pi.
10
+
11
+ ## The one command
12
+
13
+ ```
14
+ /skill:build "let admins impersonate a user for support"
15
+ ```
16
+
17
+ That is the whole learning curve on Pi. On Claude Code it is `/devos:build "..."`, on Copilot and Codex the bare `build "..."`.
18
+
19
+ DevOS reads the request, looks at the code it touches, and picks a route. There are eight.
20
+
21
+ | Size | The request looks like | What DevOS runs |
22
+ | -------------- | --------------------------------------------------------------------------- | ----------------------------------------------------- |
23
+ | **F** fog | a bare ticket title, a wish, an epic: it does not say what to change | frames it into tickets you can route, no code |
24
+ | **S** small | a typo, a one-line fix, an obvious tweak | just does it, no spec, no gate |
25
+ | **M** medium | a few files, clear behavior, a couple of edge cases | a one-page mini-spec, your go, then implement |
26
+ | **L** large | a user-visible feature, several files, requirements you would have to guess | `/devos:spec` then `/devos:implement` |
27
+ | **B** broken | something is broken and the cause is not obvious | reproduces first, then sizes the fix |
28
+ | **C** reshape | a rename, a split, a framework upgrade, behavior unchanged | an invariant spec, then proves nothing else moved |
29
+ | **H** hard | a direct attempt already failed a runnable check | manager plus fresh workers, the check is ground truth |
30
+ | **R** research | "should we use Redis or in-memory here?" | a timeboxed investigation ending in findings, no code |
31
+
32
+ The C route has a second shape for a change that spans many units, or that moves code to a stack the project does not run today: a verdict first, a unit manifest the filesystem tracks, the shared decisions made once in your own rule files, and a judgment that runs against both trees. The manifest in the spec folder is what selects that shape, so a change that is not at scale reads none of it.
33
+
34
+ ### The lifecycle
35
+
36
+ Every route lands somewhere on the same five stages. Only the size decides how much of the middle runs.
37
+
38
+ ```
39
+ once per project every change
40
+ ──────────────── ───────────────────────────────────────────
41
+
42
+ /devos:init ──▶ FRAME ──▶ DEFINE ──▶ PLAN ──▶ BUILD ──▶ VERIFY ──▶ CLOSE
43
+ map · vocabulary │ │ │ │ │ │
44
+ product knowledge │ │ │ │ │ ├─ /devos:status
45
+ wire AGENTS.md │ │ │ │ │ │ where every spec stands
46
+ │ │ │ │ │ │
47
+ │ │ │ │ │ ├─ /devos:learn
48
+ │ │ │ │ │ │ keep a durable lesson
49
+ │ │ │ │ │ │
50
+ │ │ │ │ │ └─ behaviors updated
51
+ │ │ │ │ │ spec archived
52
+ │ │ │ │ │
53
+ │ │ │ │ ├─ verifier agent (automatic)
54
+ │ │ │ │ │ runs the project's own checks
55
+ │ │ │ │ │
56
+ │ │ │ │ └─ /devos:review [--gaps]
57
+ │ │ │ │ conventions review,
58
+ │ │ │ │ or a completeness scan
59
+ │ │ │ │
60
+ │ │ │ └─ /devos:implement Phase B
61
+ │ │ │ code + tests
62
+ │ │ │
63
+ │ │ └─ /devos:implement Phase A
64
+ │ │ spec.md (the plan capsule)
65
+ │ │ ══ GATE: you approve the plan ══
66
+ │ │
67
+ │ └─ /devos:build or /devos:spec
68
+ │ interview, then spec.md
69
+ │
70
+ └─ /devos:frame only when the ask does not say what to change
71
+ brief · impact · questions · tickets, then one route per ticket
72
+ ```
73
+
74
+ Every entry command: `build` is the router, `spec` drives the interview yourself, `implement` runs an approved spec (and resumes it), `init` runs once per project. `status`, `review`, and `learn` inspect or close work at any point.
75
+
76
+ Two gates block mechanically, not by asking the model nicely. Nothing is built before you approve the plan, and nothing is called done without a verification report that names the commands that passed. On an S route there is no plan to approve, and that is correct.
77
+
78
+ ## Install
79
+
80
+ Each tool installs DevOS through its own plugin or package command. No clone needed:
81
+
82
+ ```bash
83
+ pi install npm:@tduyng/pi-devos # Pi
84
+ claude plugin marketplace add https://gitlab.com/tduyng/devos.git && claude plugin install devos@devos # Claude Code
85
+ codex plugin marketplace add https://gitlab.com/tduyng/devos.git # Codex CLI
86
+ copilot plugin marketplace add https://gitlab.com/tduyng/devos.git && copilot plugin install devos@devos # Copilot CLI
87
+ ```
88
+
89
+ Cursor copies the plugin from a clone (`just cursor-install`, see [`docs/install/cursor.md`](docs/install/cursor.md)). OpenCode V2 points `opencode.json` at a clone too, because it has no marketplace and its package route cannot reach DevOS's gate scripts.
90
+
91
+ Editing DevOS itself? Clone and install the path instead:
92
+
93
+ ```bash
94
+ git clone https://gitlab.com/tduyng/devos.git ~/code/devos
95
+ pi install ~/code/devos
96
+ ```
97
+
98
+ Every tool also takes the git remote directly: `pi install git:gitlab.com/tduyng/devos`, `claude plugin marketplace add https://gitlab.com/tduyng/devos.git`, `codex plugin marketplace add https://gitlab.com/tduyng/devos.git`, `copilot plugin marketplace add https://gitlab.com/tduyng/devos.git`. Per-tool install, update and uninstall commands are in [`docs/install/`](docs/install/).
99
+
100
+ Then, once per project:
101
+
102
+ ```
103
+ /skill:init # maps the codebase, defines vocabulary, wires AGENTS.md
104
+ /skill:build "your first real task"
105
+ ```
106
+
107
+ Onboarding runs in the background too: if you skip it and run `build`, the router notices the project is unmapped and runs it first.
108
+
109
+ Per-tool detail is in [`docs/install/`](docs/install/).
110
+
111
+ ## A worked example
112
+
113
+ ```
114
+ $ /skill:build "let users export their invoices as PDF"
115
+
116
+ Sizing: L. Touches the report layer, has open questions.
117
+ Before I start:
118
+ · Who can export: all users, or admins only?
119
+ · Include line items, or a summary only?
120
+ · Any size ceiling on a single export?
121
+
122
+ > admins only, line items, cap at 10k rows
123
+
124
+ Wrote the spec: devos/specs/2026-09-13-invoice-export/spec.md
125
+ Read the Behavior delta, then I'll plan.
126
+
127
+ $ (you read it, say go)
128
+
129
+ Plan written to spec.md. Files: 4. Task groups: 3.
130
+ GATE: approve to start building.
131
+
132
+ > go
133
+
134
+ Building... verifier running `npm test` (0, 214 passed), `npm run lint` (0)...
135
+ Verdict: DONE. verification.md written.
136
+ ```
137
+
138
+ ## Commands
139
+
140
+ You only need the first one. The rest are for when you want to drive a stage yourself or look something up.
141
+
142
+ | Command | What it does |
143
+ | ------------------------ | ---------------------------------------------------------------------------------------- |
144
+ | `/devos:build "..."` | Size any change and run the right process. Start here. |
145
+ | `/devos:frame "..."` | Turn a bare ticket or a wish into a brief, an impact map, owned questions and tickets. |
146
+ | `/devos:absorb <source>` | Record what the product promises from a help centre or a published policy. |
147
+ | `/devos:spec` | Interview you and write the functional spec, without building. |
148
+ | `/devos:implement` | Plan, build, and verify an approved spec. Resume-aware. |
149
+ | `/devos:init` | Map the codebase, define vocabulary, wire AGENTS.md. Once per project. |
150
+ | `/devos:status` | Where every spec stands. `--cost` for framework cost, `--compare a b` for a spec diff. |
151
+ | `/devos:review` | Review a diff against this project's own conventions. `--gaps` for a completeness check. |
152
+ | `/devos:learn` | File a durable lesson so it stops recurring. |
153
+
154
+ Three rules ride inside `implement`, with no command to type: stay inside the agreed scope, never weaken a test to make it pass, and name the evidence before claiming done. A hook enforces the second on every edit, on every route.
155
+
156
+ ## What lives in your repo
157
+
158
+ Everything DevOS writes goes under `devos/`, version-controlled with your code:
159
+
160
+ ```
161
+ devos/
162
+ ├── standards/
163
+ │ ├── conventions.md project decisions: checks, architecture, hard rules
164
+ │ └── rules/ scoped rules, one file per rule, attached by glob
165
+ ├── product/
166
+ │ ├── codebase-map.md where things live
167
+ │ ├── domain-model.md shared vocabulary, one page
168
+ │ ├── glossary.md the product's words, mapped to the code's
169
+ │ ├── capabilities.md each capability: articles, paths, entities, owner
170
+ │ ├── personas.md who acts, through which channel, on which tier
171
+ │ ├── constraints.md what law, contracts and platforms forbid
172
+ │ ├── knowledge/ rules distilled from sources outside the repo
173
+ │ └── behaviors/ what the product does today
174
+ ├── frames/2026-11-11-feat-1234/
175
+ │ └── frame.md context, today, expected, rules, impact, scope, questions, tickets
176
+ ├── specs/2026-09-13-invoice-export/
177
+ │ ├── spec.md the contract
178
+ │ ├── spec.md the approved plan
179
+ │ ├── decisions.md the choices made, and the ones rejected
180
+ │ ├── gates.md the checks a test cannot decide, when there are any
181
+ │ ├── manifest.tsv the units of a change that spans many files
182
+ │ └── verifications/ the proof it works
183
+ └── deferred.md real findings, out of scope for now
184
+ ```
185
+
186
+ There is no state file. Progress is derived from which files exist, so any session can resume any spec.
187
+
188
+ ## Why it stays cheap
189
+
190
+ About 298 tokens per session in pi: the skill catalog the harness renders at startup. Nothing else loads until you type a command, and the scope, test and evidence rules load with `implement`, where they apply. `/devos:status --cost` shows the numbers for your install.
191
+
192
+ ## The evidence router
193
+
194
+ The review and planning stages read your declared evidence through a small script that ships with the plugin. It picks blocks by matching words, so it needs nothing installed beyond Python 3 and its standard library. The output is a reading list and nothing gates on it. [`docs/evidence-router.md`](docs/evidence-router.md) has the flags and the scope.
195
+
196
+ ## Docs
197
+
198
+ | Page | What it covers |
199
+ | ---------------------------------------------------- | ---------------------------------------- |
200
+ | [`docs/getting-started.md`](docs/getting-started.md) | First project, step by step |
201
+ | [`docs/concepts.md`](docs/concepts.md) | The moving parts and the lifecycle |
202
+ | [`docs/evidence-router.md`](docs/evidence-router.md) | The optional evidence selector, measured |
203
+ | [`docs/README.md`](docs/README.md) | Everything else |
204
+
205
+ ## License
206
+
207
+ See [LICENSE](LICENSE).
package/package.json CHANGED
@@ -1,6 +1,46 @@
1
1
  {
2
2
  "name": "@tduyng/pi-devos",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "0.14.0",
4
+ "type": "module",
5
+ "description": "DevOS for Pi. The Pi package for DevOS, a lazy SDD framework for one engineer or a small team: adaptive sizing, a spec-driven pipeline with an approval gate, evidence-based verification. Install with `pi install npm:@tduyng/pi-devos`. Zero dependencies.",
6
+ "keywords": [
7
+ "pi",
8
+ "pi-package",
9
+ "pi-coding-agent",
10
+ "devos",
11
+ "spec-driven-development",
12
+ "coding-agents",
13
+ "skills",
14
+ "extensions"
15
+ ],
16
+ "homepage": "https://gitlab.com/tduyng/devos",
17
+ "bugs": {
18
+ "url": "https://gitlab.com/tduyng/devos/-/issues"
19
+ },
20
+ "repository": {
21
+ "type": "git",
22
+ "url": "git+https://gitlab.com/tduyng/devos.git"
23
+ },
24
+ "license": "Apache-2.0",
25
+ "author": {
26
+ "name": "tduyng"
27
+ },
28
+ "publishConfig": {
29
+ "access": "public"
30
+ },
31
+ "pi": {
32
+ "skills": [
33
+ "plugins/devos/skills"
34
+ ],
35
+ "extensions": [
36
+ "plugins/devos/pi/extension/devos.ts"
37
+ ]
38
+ },
39
+ "files": [
40
+ "plugins/devos/skills/",
41
+ "plugins/devos/scripts/",
42
+ "plugins/devos/agents/",
43
+ "plugins/devos/pi/extension/devos.ts",
44
+ "CHANGELOG.md"
45
+ ]
46
+ }
@@ -0,0 +1,27 @@
1
+ ---
2
+ name: reader
3
+ description: Fresh-context reader for a plan capsule. Names every decision the plan leaves to whoever executes it. Run it on spec.md before the plan gate, with no access to the conversation that wrote it.
4
+ ---
5
+
6
+ You are the **Reader**. A plan was written for a change you know nothing about, and a later session executes it with the same ignorance you have now. Your job is to find where that execution would have to guess.
7
+
8
+ You get one file, `spec.md`. Do not read the conversation that produced it, and do not treat the repository as context: open a file only to resolve a path or symbol the plan itself names, and never to reconstruct an intent the plan left out. Intent you had to go and find is intent the plan failed to carry.
9
+
10
+ ## The test
11
+
12
+ Walk the plan as its executor. At each task group, ask what you would have to decide before writing the first line: the shape of a value, the error path, which of two existing helpers to call, where a new file comes from, what happens on empty and on duplicate input, which layer owns a behavior. A decision is anything where two competent engineers would write different code and both could say the plan told them to.
13
+
14
+ A plan that settles a decision explicitly has settled it. A plan that never mentions it has not, and that silence is what you report.
15
+
16
+ ## Report
17
+
18
+ Plain text back to the caller, no file written.
19
+
20
+ ```
21
+ VERDICT: pass | gaps
22
+ 1. <the plan path or task group>: <the decision it leaves open, and what you would have to invent>
23
+ ```
24
+
25
+ At most ten, most consequential first. When you could execute the plan as written, report `pass` and stop. Leave out style, naming taste, and scope ("this should not be built"), plus anything the plan puts under **Never** or **Ask First**: the author said those out loud, and repeating them buries the ones they did not. Whether the work already exists on disk is the verifier's completeness lens, not yours.
26
+
27
+ Do not ask a question. Nobody is here to answer it, and the question is the finding: write what you would have had to ask.