solveos-cli 0.1.0

package/templates/config-default.json

@@ -0,0 +1,21 @@
+{
+  "mode": "interactive",
+  "gates": {
+    "research": true,
+    "plan_validation": true,
+    "build_validation": true,
+    "review_pre_ship": true,
+    "review_post_ship": true
+  },
+  "plan_validation_max_passes": 3,
+  "granularity": "standard",
+  "auto_advance": false,
+  "domain": "software",
+  "runtime": "auto",
+  "hooks": {
+    "context_monitor": true,
+    "context_monitor_threshold": 60,
+    "brief_anchor": true,
+    "brief_anchor_interval": 10
+  }
+}

package/templates/plan-brief.md

@@ -0,0 +1,106 @@
+# Plan Brief
+
+<!-- This is the central artifact of your solveOS cycle.
+     Every answer here becomes an instruction for AI execution.
+     Every ambiguity becomes a guess in the output.
+     Be specific. Be honest. Leave nothing implied. -->
+
+## Problem
+
+<!-- What is broken, missing, or needed?
+     Write 1-2 sentences. State the problem, not the solution.
+     Bad:  "We need to add a caching layer."
+     Good: "API response times exceed 2 seconds under load, causing user drop-off." -->
+
+_Replace this with a clear problem statement._
+
+## Audience
+
+<!-- Who experiences this problem? Be specific.
+     Name a person, role, or group — not "everyone" or "users."
+     Bad:  "Users"
+     Good: "Backend engineers on the payments team who deploy 3x/day." -->
+
+_Replace this with your target audience._
+
+## Goal
+
+<!-- What does success look like? One sentence, starts with a verb.
+     This is the finish line — how you know you're done.
+     Bad:  "Improve performance."
+     Good: "Reduce p95 API response time to under 500ms at current load." -->
+
+_Replace this with a concrete goal._
+
+## Appetite
+
+<!-- How much time/effort are you willing to invest?
+     This is a bet, not an estimate. It sets the scope ceiling.
+     If you'd only spend 2 hours on this, say so. That shapes the plan.
+     Bad:  "As long as it takes."
+     Good: "4 hours of focused work. If it's not done by then, we re-scope." -->
+
+_Replace this with your appetite._
+
+## Constraints
+
+<!-- What are the non-negotiables? Skills, dependencies, existing decisions.
+     List anything that limits how the work can be done. -->
+
+- _Constraint 1_
+- _Constraint 2_
+
+## Success Criteria
+
+<!-- How will you know it's done? Each criterion must be:
+     - Measurable (a human or test can verify it)
+     - Falsifiable (you can prove it failed)
+     Use checkbox format. These become your build validation checklist. -->
+
+- [ ] _Criterion 1_
+- [ ] _Criterion 2_
+- [ ] _Criterion 3_
+
+## Core Assumption
+
+<!-- What must be true for this plan to work?
+     Every plan has a bet underneath it. Name it explicitly.
+     If this assumption is wrong, the plan may need to change.
+     Bad:  "This should work."
+     Good: "The existing database schema can support the new query pattern
+            without migration." -->
+
+_Replace this with your core assumption._
+
+## Rabbit Holes
+
+<!-- What unknowns could drag the build off track?
+     These are areas where you could lose time exploring without progress.
+     Naming them is a defense mechanism — it makes you notice when you're in one. -->
+
+- _Rabbit hole 1_
+- _Rabbit hole 2_
+
+## Out of Scope
+
+<!-- What are you explicitly NOT solving in this cycle?
+     Saying "not this" is as important as saying "this."
+     Prevents scope creep and mid-build pivots. -->
+
+- _Out of scope item 1_
+- _Out of scope item 2_
+
+---
+
+<!-- Plan Phase Exit Checklist (from solveOS framework):
+     Before moving to Build, verify:
+     [ ] Problem is stated without embedding a solution
+     [ ] Audience is specific (not "users" or "everyone")
+     [ ] Goal starts with a verb and is one sentence
+     [ ] Appetite is a bet, not an estimate
+     [ ] Constraints are listed (even if few)
+     [ ] Every success criterion is measurable and falsifiable
+     [ ] Core assumption is explicit and testable
+     [ ] At least one rabbit hole is identified
+     [ ] Out of scope is non-empty
+     [ ] A stranger could read this brief and build from it -->

package/templates/plan-validation-log.md

@@ -0,0 +1,77 @@
+## Plan Validation Log — Pass {n}
+
+**Date:** _YYYY-MM-DD_
+**Pass:** _{n} of {max}_
+
+---
+
+### Question 1: Is the problem correctly stated?
+
+<!-- Is this the actual problem, or a symptom? Is the audience named specifically?
+     Could someone outside the project understand what's wrong? -->
+
+**Assessment:** _Pass / Gaps found_
+
+**Details:**
+_Explanation of assessment_
+
+**Gaps (if any):**
+- _Gap description_
+
+---
+
+### Question 2: Is the plan feasible?
+
+<!-- Can the goal be achieved within the stated constraints and appetite?
+     Do the constraints conflict with each other? Is the appetite realistic? -->
+
+**Assessment:** _Pass / Gaps found_
+
+**Details:**
+_Explanation of assessment_
+
+**Gaps (if any):**
+- _Gap description_
+
+---
+
+### Question 3: Is it specific enough to build from?
+
+<!-- Could someone who didn't write the brief execute it and produce the same result?
+     Would two people interpret the success criteria the same way? -->
+
+**Assessment:** _Pass / Gaps found_
+
+**Details:**
+_Explanation of assessment_
+
+**Gaps (if any):**
+- _Gap description_
+
+---
+
+### Additional Checks
+
+**Are success criteria measurable and falsifiable?**
+_Yes / No — details_
+
+**What would you cut if scope had to be reduced by 50%?**
+_Answer_
+
+**What is the single biggest unacknowledged risk?**
+_Answer_
+
+---
+
+### Summary
+
+**Gaps found:** _{count}_
+**Changes recommended:**
+- _Change 1_
+- _Change 2_
+
+### Decision
+
+- [ ] Ready to build — no critical gaps remain
+- [ ] Needs another pass — refine the brief and re-validate
+- [ ] Needs escalation — fundamental issues require research or rethink

package/templates/post-ship-review.md

@@ -0,0 +1,75 @@
+## Post-Ship Review — Cycle {n}
+
+**Date:** _YYYY-MM-DD_
+**Time since ship:** _How long since shipping_
+
+---
+
+### Success Criteria Measurement
+
+<!-- For each success criterion from the Plan Brief, measure against real-world results.
+     Use evidence, not hopes. "Users seem to like it" is not evidence.
+     "3 out of 5 users completed the flow without help" is evidence. -->
+
+| # | Criterion | Result | Evidence |
+|---|-----------|--------|----------|
+| 1 | _Criterion from BRIEF.md_ | _Met / Partially met / Not met_ | _What actually happened_ |
+| 2 | _Criterion from BRIEF.md_ | _Met / Partially met / Not met_ | _What actually happened_ |
+
+**Overall:** _{x} Met, {y} Partially met, {z} Not met out of {total}_
+
+---
+
+### What worked well?
+
+<!-- Specific decisions, approaches, or tools that produced good outcomes -->
+
+- _What worked and why_
+
+### What didn't work?
+
+<!-- Specific decisions that led to problems or waste -->
+
+- _What didn't work and why_
+
+### Most impactful decision
+
+<!-- Name the one decision — positive or negative — that mattered more than any other -->
+
+**Decision:** _The one decision that mattered most_
+**Impact:** _What happened because of this decision_
+**Lesson:** _What to do differently or repeat_
+
+---
+
+### Feed-Forward for Next Cycle
+
+<!-- These items become inputs to the next cycle's Plan Brief via /solveos:new-cycle.
+     Be specific — vague feed-forward is useless feed-forward. -->
+
+#### New problems revealed
+
+<!-- Problems that only became visible after shipping.
+     Frame as problem statements, not solutions. -->
+
+- _Problem statement_
+
+#### Deferred scope
+
+<!-- Items intentionally cut from this cycle.
+     For each: is it still important? Has the context changed? -->
+
+- _Item — still important? context changed?_
+
+#### Wrong assumptions
+
+<!-- Assumptions from the Plan Brief that turned out to be incorrect -->
+
+- _Assumption_ → _What reality showed instead_
+
+#### Open questions
+
+<!-- Questions that remain unanswered.
+     Would a Research gate help in the next cycle? -->
+
+- _Question_

package/templates/pre-ship-review.md

@@ -0,0 +1,56 @@
+## Pre-Ship Review
+
+**Date:** _YYYY-MM-DD_
+
+---
+
+### Does the result solve the stated problem?
+
+<!-- Re-read the problem field from the Plan Brief.
+     Does the build actually address this problem? -->
+
+**Assessment:** _Yes / Partially / No_
+
+**Details:**
+_Explanation of what's solved and what isn't_
+
+---
+
+### Would the named audience find this useful?
+
+<!-- Re-read the audience field from the Plan Brief.
+     Put yourself in their position. -->
+
+**Audience:** _From Plan Brief_
+**Assessment:** _Yes / Partially / No_
+
+**Details:**
+_Explanation — usefulness, usability, quality match for this audience_
+
+---
+
+### What is the weakest part?
+
+<!-- Every piece of work has a weakest part. Name it. -->
+
+**Weakest part:** _Specific description_
+
+**Impact:** _How much does this weakness matter for the stated audience?_
+
+**Decision on weakness:**
+- [ ] Accept — weakness is in a non-critical area
+- [ ] Fix — weakness is significant enough to iterate
+- [ ] Defer — add to next cycle
+
+---
+
+### Ship readiness
+
+<!-- Be honest: are you shipping because it's ready, or because you're tired?
+     Sunk cost is not a reason to ship. "Good enough" is valid only if you can
+     articulate why it's good enough for this specific audience. -->
+
+**Assessment:** _Ready to ship / Not ready — needs iteration_
+
+**Rationale:**
+_Why it's ready, or why it's not_

package/templates/research-summary.md

@@ -0,0 +1,30 @@
+## Research Summary
+
+**Question:** _Replace with the specific research question_
+**Time spent:** _Replace with duration_
+
+### Key Findings
+
+- _Finding 1_
+- _Finding 2_
+- _Finding 3_
+
+### Conclusions
+
+<!-- What do these findings mean for the Plan Brief?
+     How do they affect the problem statement, constraints, or approach? -->
+
+- _Conclusion 1_
+- _Conclusion 2_
+
+### Open Questions / Remaining Unknowns
+
+<!-- What do you still not know? What could change the plan if discovered later? -->
+
+- _Open question 1_
+- _Open question 2_
+
+### Decision
+
+- [ ] I have enough information to write the Plan Brief
+- [ ] I need more research: _specify what_