refactor: use project status JSON for skill state reads#65
Open
refactor: use project status JSON for skill state reads#65
Conversation
Set HiLL checkpoint to final phase per workflow.hillCheckpointDefault, enable auto-review at HiLL checkpoints, and transition state to implement / in_progress at p01-t01.
…son (read path only)
…t for skills - contributing/skills.md: add 'Reading project state' subsection pointing to the canonical preamble in create-oat-skill and noting the test-locked JSON contract - reference/cli-reference.md: annotate 'oat project status --json' as a stable skill contract; list locked field set - .oat/repo/reference/current-state.md: add 'Skill state reads' bullet under State + Conventions
- backlog/items/bl-281c: mark state.md slice complete (preamble pattern, fallback, contract test, docs); narrow remaining scope to plan.md / implementation.md migration + named-candidate skills not covered by the state.md grep scan; reduce priority high -> medium - roadmap: control-plane read-layer follow-through now 'In progress' with state.md slice shipped - backlog/index.md: regenerated managed marker section via 'oat backlog regenerate-index'
44d5643 to
32e0626
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
refactor: use project status JSON for skill state reads
Summary
This PR migrates OAT skills that hand-parsed project
state.mdfrontmatter to CLI-owned project status reads. The migrated skills still treatstate.mdas the source of truth, preserve existing write paths, keep null-sentinel behavior stable, and use conciseoat project status --field/--shell/--project-pathsnippets instead of local JSON plumbing.Quick-mode note: this project has discovery, plan, implementation, review, and verification artifacts, but no spec or design artifacts.
Goals / Non-Goals
nullsurfacing as the literalnullsentinel.state.mdgreps, and broader state-read migrations out of scope.oatshim backed bynpx.Changes
oat project status --field <path>for arbitrary-depth single-field reads.oat project status --shell NAME=path ...for shell-safe multi-field assignments from one project status read.oat project status --project-path <path>for repo-relative or absolute path-directed reads when a skill has already resolved the target project.create-oat-skill, including theoatPATH contract andnpx-backed shim for CI/cloud environments.oat-project-progress,oat-project-pr-progress,oat-project-plan,oat-project-pr-final,oat-project-review-provide,oat-project-reconcile, andoat-project-completeto concise--field/--shellsnippets.oat-project-review-providevia--project-pathafter final review identified that path-directed reviews still need to validate the requested worktree.0.0.50to0.0.53after rebasing onto anorigin/mainalready at0.0.52, and regenerated public package version metadata.--field,--shell,--project-path, and theoatshim contract.Verification
pnpm lintpnpm formatpnpm type-checkpnpm test(1365 tests)pnpm buildpnpm release:validate--project-pathwith--fieldand--shellReviews
Archived review artifacts are intentionally not linked because
.oat/**/reviews/archived/is configured as a local-only path.References