Ctx Core

ctx-core

**Alpha** — Built for active dogfooding. The interface is intentionally small.

A continuity-first Agent Skills plugin for Claude Code, Codex, and OMP.

Two workflows

Workflow	Use it when	State
ctx-prd	Product behavior, scope, visual direction, safety, or acceptance is unresolved	Canonical Obsidian PRD
ctx-lean	The desired outcome is settled and needs analysis, implementation, debugging, QA, or verification	Ephemeral session state

**Unsettled product decision → PRD. Settled outcome → Lean.**

Technical complexity and code size do not decide the workflow.

`ctx-prd`

`ctx-prd` turns consequential product ambiguity into a durable decision contract, then executes it gate by gate.

It:

1. Inspects existing evidence.
2. Asks one consequential question at a time.
3. Creates a concise canonical PRD in Obsidian.
4. Defines 1–5 observable vertical gates.
5. Names an automated or human verifier for each gate.
6. Waits for explicit approval.
7. Executes and updates one gate at a time.

Obsidian is required for PRD work. There is no repository Markdown fallback.

Every initiative uses one deterministic hierarchy:

/
  PRD/
    .md
  Planning/
    -g1-.md
    -g2-.md

The PRD always uses Outcome, Boundaries, Decisions, Current checkpoint, Gates, Approval, Evidence, and Amendments in that order. Every gate contains a concise Feature list and exactly one linked ctx-lean plan. Plans link back and own implementation detail, reuse decisions, lane ownership, and verification.

The PRD owns product decisions, gates, status, verifiers, and evidence links. Detailed implementation belongs to linked plans; test results remain in descriptively named QA campaign notes. Canvas is presentation-only.

A gate is not complete until the canonical PRD records its result and evidence. It cannot activate until its plan resolves, links