feat: add framework-owned templates - #25
Open
apcjoaofilho wants to merge 1 commit into
Open
Conversation
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.
What
Adds the M1 framework-owned template foundation under
templates/plus a validator script and tests.Why
Closes #1
Inline templates cannot be reused programmatically or validated. Dedicated files make the framework easier to version, copy into projects, and check in CI.
How
STATUS.md,STATE.json, project-rootAGENTS.md, andADR.md.spec-delta.mdandproject.md, both explicitly labelled as manual fallback only because OpenSpec owns native spec artifacts whenspec_engine = openspec.scripts/validate-templates.pywith--format tty|json, expected-template checks, text placeholder-header checks, manual-fallback labelling checks, andSTATE.jsonschema validation.tests/templates/test_templates.pycovering template presence, placeholder headers, STATE schema validation, manual fallback labels, validator success, and missing-template failure.templates/README.md,references/README.md, andCHANGELOG.md.Scope check
skill/PLAN.mdupdated if scope changed (new phase/template/script/flavor)CHANGELOG.mdentry added under[Unreleased]ruff check .passespytestpasses (where applicable)Notes for reviewers
templates/handoff-schema.yamlis left to M12, wherescripts/handoff.pycan validate it alongside backend behavior.templates/STATE.jsoncannot start with a comment because it must remain valid JSON and validate againstreferences/state-schema.json; the validator treats it as the only header-comment exception.ruff check .,pytest -q,python scripts/validate-templates.py --format json,python scripts/validate-state.py templates/STATE.json --format json, andgit diff --check.