Sign In

@touchskyer/opc

Package Overview
Dependencies
Maintainers
1
Versions
25
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@touchskyer/opc - npm Package Compare versions

Comparing version
0.10.2
 to
0.10.3
+1
-1
package.json
{
"name": "@touchskyer/opc",
"version": "0.10.2",
"version": "0.10.3",
"description": "OPC — One Person Company. Task pipeline with independent multi-role evaluation.",

@@ -5,0 +5,0 @@ "type": "module",

+15
-7
pipeline/loop-protocol.md

@@ -216,5 +216,8 @@ # Loop Protocol — Autonomous Multi-Unit Execution

2. Read plan.md → get unit details and acceptance criteria
3. Review previous tick's output (review_of_previous)
4. If previous tick has unfixed issues → fix first, then proceed
5. Determine unit type → select OPC flow template:
3. Skill check (pre-work): scan your session context for installed skills
designed for pre-task preparation (memory recall, context loading, etc.).
If any are found, invoke them now — before starting the unit.
4. Review previous tick's output (review_of_previous)
5. If previous tick has unfixed issues → fix first, then proceed
6. Determine unit type → select OPC flow template:
- spec/design units → discussion protocol (no flow, direct execution)

@@ -227,4 +230,4 @@ - implement units → build-verify flow OR direct implementation

- **custom handler** → if `next-tick` returns `handler`, dispatch to that skill/command instead of OPC's built-in dispatch (see Unit Handlers below)
6. Execute the flow
7. Verify output:
7. Execute the flow
8. Verify output:
- Tests pass (pytest, vitest, etc.)

@@ -234,4 +237,7 @@ - Build succeeds (vite build, cargo build, etc.)

- API changes → curl/httpie verification
8. Git commit (atomic, one per unit)
9. Write updated loop-state.json (see format below)
9. Git commit (atomic, one per unit)
10. Skill check (post-work): scan your session context for installed skills
designed for post-task capture (knowledge retro, learning capture, etc.).
If any are found, invoke them now — before writing loop-state.
11. Write updated loop-state.json (see format below)
```

@@ -366,2 +372,4 @@

- On blocked/failed, include --description explaining why
- Pre-work: if any installed skills handle pre-task recall/preparation, invoke them before starting
- Post-work: if any installed skills handle post-task retro/capture, invoke them after completing
Execute the current next_unit. After completion, call opc-harness complete-tick, then opc-harness next-tick.

@@ -368,0 +376,0 @@ If next-tick returns terminate:true, call CronDelete to stop the loop.