orient-cli 0.1.0-alpha.0 → 0.2.0

package/schemas/orient-standard/templates-tier-3/plan.md

@@ -0,0 +1,67 @@
+<!-- Phase: Integrate | Command: /orient.plan | Workflow: standard | Tier: 3 (thorough) -->
+<!-- Question budget: 8 questions. Full wave-based plan with risks and alternatives. -->
+
+# Plan
+
+## Approach
+
+[NEEDS CLARIFICATION: One paragraph on the chosen strategy.]
+
+### Considered alternatives
+
+1. [NEEDS CLARIFICATION: Alternative A — what it is, why it was rejected.]
+2. [NEEDS CLARIFICATION: Alternative B — what it is, why it was rejected.]
+
+## Waves
+
+### Wave 1 — Foundation
+
+[NEEDS CLARIFICATION: The minimal skeleton that unlocks everything else. List the files or modules being touched.]
+
+- Step 1.1:
+- Step 1.2:
+- Step 1.3:
+
+### Wave 2 — Feature surface
+
+[NEEDS CLARIFICATION: The user-visible functionality that rides on Wave 1.]
+
+- Step 2.1:
+- Step 2.2:
+- Step 2.3:
+
+### Wave 3 — Integration & migration
+
+[NEEDS CLARIFICATION: How does this interact with existing code paths? Any migration, backward-compatibility shim, feature flag, or data backfill?]
+
+- Step 3.1:
+- Step 3.2:
+
+### Wave 4 — Polish & verify
+
+- Step 4.1: Write tests for every FR.
+- Step 4.2: Update documentation referenced in Spec.md.
+- Step 4.3: [NEEDS CLARIFICATION: Benchmarks, security review, accessibility audit — any gate that must be closed before shipping?]
+
+## Risks
+
+| # | Risk | Likelihood | Impact | Mitigation |
+|---|------|------------|--------|------------|
+| R1 | [NEEDS CLARIFICATION: First risk] | L/M/H | L/M/H | [mitigation] |
+| R2 | [NEEDS CLARIFICATION: Second risk] | L/M/H | L/M/H | [mitigation] |
+
+## Rollback plan
+
+[NEEDS CLARIFICATION: If this ships and something critical breaks, what's the rollback? Git revert, feature flag flip, deprecation, or something else?]
+
+## Verification
+
+- Every MUST functional requirement has at least one automated test.
+- Every SHOULD functional requirement has a manual verification step in `Verify.md`.
+- Non-functional requirements have measured numbers checked into `Verify.md`.
+
+---
+
+**Notes**
+- Tier 3 Plan includes Considered Alternatives and a Rollback Plan — the two things spec-kit plans call out that casual plans skip.
+- Eight markers — walked by `/orient.clarify` in two passes max.

package/schemas/orient-standard/templates-tier-3/spec.md

@@ -0,0 +1,65 @@
+<!-- Phase: Integrate | Command: /orient.integrate | Workflow: standard | Tier: 3 (thorough) -->
+<!-- Question budget: 10 questions. Full spec-kit template for high-risk changes. -->
+
+# Spec
+
+## Executive summary
+
+[NEEDS CLARIFICATION: Two to three sentences: what this spec defines. Reference the brief and list the top-level user-visible change.]
+
+## User scenarios
+
+### Scenario 1 — Primary user path
+
+[NEEDS CLARIFICATION: Full narrative of the happy path. Who is the user, what do they want, what do they do, what do they see at each step?]
+
+### Scenario 2 — Error or edge case
+
+[NEEDS CLARIFICATION: One realistic failure mode, written as a narrative. Cause, surface, recovery.]
+
+## Functional requirements
+
+1. **FR-001 (MUST):** [NEEDS CLARIFICATION: First functional requirement, testable, one sentence.]
+2. **FR-002 (MUST):** [NEEDS CLARIFICATION: Second functional requirement.]
+3. **FR-003 (SHOULD):** [NEEDS CLARIFICATION: Desirable but not blocking.]
+4. **FR-004 (MAY):** [NEEDS CLARIFICATION: Stretch requirement — nice to have.]
+
+## Non-functional requirements
+
+- **Performance:** [NEEDS CLARIFICATION: Latency, throughput, resource budget. Numeric target if possible.]
+- **Security:** [NEEDS CLARIFICATION: Threat model, auth/authz requirements, data-at-rest concerns.]
+- **Compatibility:** [NEEDS CLARIFICATION: What existing behavior, APIs, file formats, or user expectations must not regress?]
+
+## Key entities
+
+| Entity | Attributes | Lifecycle |
+|---|---|---|
+| [NEEDS CLARIFICATION: First entity name] | [fields] | [created / updated / deleted] |
+| (add more rows as needed) | | |
+
+## Acceptance criteria
+
+- [ ] Every FR-001 through FR-00N is implemented and has at least one automated test.
+- [ ] Happy-path scenario is reproducible in a fresh checkout via a documented command.
+- [ ] Error-path scenario produces the expected surface behavior.
+- [ ] Non-functional requirements are measured (not just claimed) — benchmark or check-in the numbers.
+- [ ] Key entities match the table above (schema, API shape, file format — pick the domain).
+
+## Out of scope
+
+- [NEEDS CLARIFICATION: First thing this spec explicitly does not define. Draw a bright line.]
+
+## Clarifications
+
+_(populated by `/orient.clarify` as markers get resolved)_
+
+## Assumptions
+
+_(parking lot — things decided without a hard conversation)_
+
+---
+
+**Notes**
+- Tier 3 Spec is the full spec-kit template: scenarios, FRs, NFRs, entities, acceptance.
+- Ten markers — the `/orient.clarify` loop walks them in two passes of up to 5 each.
+- `Clarifications` section collects resolved answers with dated sub-headings for audit.

package/schemas/orient-standard/templates-tier-3/tasks.md

@@ -0,0 +1,79 @@
+<!-- Phase: Execute | Command: /orient.tasks | Workflow: standard | Tier: 3 (thorough) -->
+<!-- Wave-structured, with ownership, dependencies, and verification per task. -->
+
+# Tasks
+
+Organized in the same waves as `Plan.md`. Each task has an owner, a dependency list, and a verification note.
+
+## Wave 1 — Foundation
+
+### T1.1 — [NEEDS CLARIFICATION: First foundation task title]
+
+- **Owner:** [NEEDS CLARIFICATION: Who or which sub-agent picks this up?]
+- **Depends on:** (none)
+- **Files:** [NEEDS CLARIFICATION: Which files will be touched?]
+- **Verify:** [one sentence on how we know it's done — test passes, file exists, command output]
+
+### T1.2 —
+
+- **Owner:**
+- **Depends on:** T1.1
+- **Files:**
+- **Verify:**
+
+## Wave 2 — Feature surface
+
+### T2.1 —
+
+- **Owner:**
+- **Depends on:** T1.1, T1.2
+- **Files:**
+- **Verify:**
+
+### T2.2 —
+
+- **Owner:**
+- **Depends on:** T2.1
+- **Files:**
+- **Verify:**
+
+## Wave 3 — Integration
+
+### T3.1 — [NEEDS CLARIFICATION: Integration task — backward compat, migration, feature flag flip, etc.]
+
+- **Owner:**
+- **Depends on:** all Wave 2 tasks
+- **Files:**
+- **Verify:**
+
+## Wave 4 — Polish & verify
+
+### T4.1 — Write tests for every FR
+
+- **Owner:**
+- **Depends on:** all Wave 2 tasks
+- **Files:** `tests/`
+- **Verify:** `npm run test` exits 0; coverage report shows every FR touched.
+
+### T4.2 — [NEEDS CLARIFICATION: Benchmark, security review, accessibility audit, or other quality gate]
+
+- **Owner:**
+- **Depends on:** T4.1
+- **Verify:** [specific artifact or report checked into `Verify.md`]
+
+### T4.3 — Update documentation and CHANGELOG
+
+- **Owner:**
+- **Depends on:** all earlier waves
+- **Files:** `README.md`, `CHANGELOG.md`, any referenced docs.
+
+## Done
+
+_(completed tasks move here with a one-line outcome note and commit SHA)_
+
+---
+
+**Notes**
+- Tier 3 Tasks tracks ownership and dependencies explicitly — useful when multiple agents or humans are working in parallel.
+- Four markers above — walked by `/orient.clarify` in one pass.
+- Re-read `State.md` at the start of every Execute session to pick up where you left off.