-
Notifications
You must be signed in to change notification settings - Fork 0
Changelog
This page summarizes recent wiki-relevant releases. The authoritative release history remains the repository CHANGELOG.md, GitHub Releases, and git tags.
Note
Wiki summaries intentionally focus on user-facing documentation changes and workflow boundaries. Use the repository changelog for exact release notes.
Adds issue-comment discipline, context-aware requirement grilling, vertical-slice breakdown wording, and a TDD tracer-bullet guide.
Visible documentation points:
-
guides/templates/issue-tracking-comments.mdprovides pickup, progress/blocker, and completion comment drafts for issue-based work. -
/requirementsnow challenges glossary conflicts, fuzzy terms, scenarios, code contradictions, and ADR conflicts when repo context exists. -
/breakdownnow prefers backlog-bound tasks that are independently verifiable vertical slices. -
/build-briefcan loadguides/tdd-tracer-bullet.mdfor TDD, red-green-refactor, or test-first work. - Codex update-flow docs and GitHub Actions/link-check maintenance commits since v2.21.6 are included in this tag.
Boundary: markdown guidance only. No automatic issue mutation, setup engine, test runner, runtime enforcement, or dynamic orchestration.
Fixes Codex v0.137.0 startup compatibility for the package SessionStart hook.
Visible documentation points:
-
hooks/session-start.shreturns valid JSON withhookSpecificOutput.additionalContextwhen Codex invokes the hook. - Claude/default runs still emit the markdown reminder directly.
-
tests/test-verbosity-hook.shnow includes a Codex JSON parse smoke test. - Compatibility docs now describe this as a narrow output adapter rather than Claude hook feature parity.
Boundary: hook-output compatibility only. No runtime enforcement, policy authorization, dynamic orchestration, or general Claude hook port to Codex.
Adds optional repo-local context guidance so skills can read glossary, issue-tracker, triage-label, domain-doc, and ADR context before reasoning.
Visible documentation points:
- New
guides/project-context-contract.mddefines optional context files such asCONTEXT.md,CONTEXT-MAP.md, anddocs/agents/*.md. -
/requirements,/design,/build-brief,/diagnose, and/scrutinizenow check glossary/context files when present. -
/breakdownand the AGENT-BRIEF template now classify backlog-bound work asready-for-agent,ready-for-human, orneeds-info. -
llms.txtindexes the guide for cross-agent discovery.
Boundary: markdown guidance only. No setup engine, automatic issue mutation, runtime enforcement, marketplace behavior change, or Claude hook port to Codex.
Adds explicit release classification so maintainers choose release now, bundle later, or no release before version files change.
Visible documentation points:
-
/deploy-guidenow includes a plugin release decision gate. -
CONTRIBUTING.mdmirrors the same three categories in the release checklist. -
tests/validate-content.shpins the gate so the workflow does not drift back into implicit release decisions.
Boundary: markdown workflow guidance and validation only. No runtime enforcement, marketplace behavior change, skill automation, or Claude hook port to Codex.
Adds concise repo-local context for Codex and other non-Claude agents.
Visible documentation points:
-
DOMAIN.mdcaptures invariants, safety rules, data boundaries, and validation expectations. -
SPEC.mdprovides a fast project digest and session re-entry context. -
.codex/README.mddocuments repo-local Codex setup and the Claude-hook boundary. -
docs/adr/README.mdand ADR-025 record the ADR index and project-context decision. -
AGENTS.mdandllms.txtpoint agents at these context files.
Boundary: documentation and session ergonomics only. No runtime enforcement, marketplace behavior change, skill behavior change, or Claude hook port to Codex.
Fixes the Codex installed-cache validator context without changing skill behavior.
Visible documentation points:
-
tests/validate-structure.shnow accepts the installed-cache shape where Codex omitsplugin -> .because the installed root is already the plugin root. - Source and marketplace snapshots still require
plugin -> .for publishability, because the Codex marketplace descriptor points at./plugin. -
docs/codex-integration.mdexplains when to run source/marketplace validation versus installed-cache validation.
Boundary: packaging validation and documentation only. No runtime enforcement, marketplace behavior change, skill behavior change, or Claude hook port to Codex.
Adds explicit limitations and release-evidence guidance for cross-agent users.
Visible documentation points:
- New Limitations page explaining where the plugin helps, what it does not enforce, and what evidence belongs in PR/release proof.
-
docs/compatibility-matrix.mdnow compares shared markdown skills, Claude Code packaging, Codex packaging, hooks, memory, enforcement, and release evidence. -
CONTRIBUTING.mdnow asks PRs that affect user-facing doctrine, install, release, generated catalog, or runtime-boundary surfaces to include real behavior proof. -
tests/validate-structure.shnow keeps the Limitations page in the required wiki skeleton.
Boundary: documentation and release discipline only. No runtime enforcement, package behavior change, marketplace behavior change, or Claude hook port to Codex.
Adds a generated skill catalog and documents the shared SKILL.md frontmatter contract for Claude Code, Codex, and other markdown-capable agents.
Visible documentation points:
-
docs/data/skills.jsonis generated fromskills/*/SKILL.mdfor cross-agent discovery. -
CONTRIBUTING.md,guides/skill-authoring.md, anddocs/compatibility-matrix.mddocument required, optional, cross-agent, and Codex-ingestible frontmatter fields. -
docs/codex-integration.mdandllms.txtpoint tools to the generated catalog. -
guides/structured-output-protocol.mdadds a compact handoff-integrity note pattern. -
/review-ai,/reflect, andguides/quick-reference.mdadd observable AI-work health signals such as loops, retries, context compaction, audit evidence, and next-session recovery.
Boundary: generated metadata and markdown guidance only. No runtime dispatcher, no Claude hook port to Codex, no budget enforcement, no policy gate, and no agent-to-agent orchestration protocol.
/deploy-guide now covers provider-managed production canaries and capacity changes where the requested canary target and the provider-selected target may differ.
Visible documentation points:
- Precheck, cordon, observation, drain, provider-side change, reconciliation, and postcheck phases.
- Planned target vs actual provider-selected target comparison.
- Desired/min/max capacity, readiness, schedulable capacity, and unintended
SchedulingDisabledchecks. - Unresolved rollout state routes to
/operational-state.
Boundary: no cloud execution, policy enforcement, Kubernetes automation, ASG automation, or runtime state engine.
/consistency-check now includes a lightweight mode for incident and config hotfix work that does not have persisted spec artifacts.
Visible documentation points:
- Checks symptom, evidence, root cause, actual fix, deploy path, live verification, and drift.
- Flags overclaiming PR/changelog text, missing evidence, scope mismatch, deploy drift, and unclassified adjacent operational state.
- Routes unresolved related findings to
/operational-state.
Boundary: no runtime enforcement, cloud execution, alert mutation, or automatic issue closure.
Adds /operational-state, a read-only classifier for operational findings.
States:
- Watch
- Fix Candidate
- Active Incident
- Resolved
- Handoff
- Known Accepted Issue
- False Positive
- Self-Resolved
The skill maps each state to evidence, allowed and prohibited actions, approval gates, artifacts, escalation criteria, and closure criteria.
Boundary: no runtime state engine, policy enforcement, cloud execution, alert suppression automation, or automatic production write.
Ships doctrine-only improvements to existing skills:
-
/deploy-guideclassifies deploy type before rollout planning. -
/security-checkcovers more infrastructure and configuration surfaces. -
/reflectcaptures more granular skill-effectiveness feedback. -
/management-talkincludes an operational incident closure example.
Broader operational model work was intentionally deferred until later releases.
Clarifies that Codex can install the plugin and load the same markdown skills, but does not run Claude hooks or gain runtime enforcement.
Related docs:
Adds Codex packaging through .codex-plugin/plugin.json and .agents/plugins/marketplace.json while preserving the Claude Code package.
Install path:
codex plugin marketplace add pitimon/8-habit-ai-dev
codex plugin add 8-habit-ai-dev@pitimon-8-habit-ai-devBoundary: same read-only markdown skills, no Claude hook parity, and no runtime enforcement.
For earlier versions, use:
Source of truth: this wiki is generated from docs/wiki/. Edits made through the GitHub Wiki web UI may be overwritten by the next sync. To change a page, open a PR against the repository source file.
Repository · Issues · README · License
Workflow discipline for AI-assisted development
Start
Workflow
- Overview
- 0 · Research
- 1 · Requirements
- 2 · Design
- 3 · Breakdown
- 4 · Build Brief
- 5 · Review AI
- 6 · Deploy Guide
- 7 · Monitor Setup
Operations
Reference
- Habits Reference
- Maturity Model
- Architecture
- Limitations
- Vibe Coding vs Structured
- Harness Engineering
Project