intent-records
Draft or approve an intent record when a person asks for a change, or describe existing behaviour before retrofitting compiled intent. Use before turning intent into a pi-work workspec.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- intent-records
- description
- Draft or approve an intent record when a person asks for a change, or describe existing behaviour before retrofitting compiled intent. Use before turning intent into a pi-work workspec.
03 SKILL.md 正文
Adopter records, models, receipts, conformance manifests, oracles and vendored scripts live under .intent/ (.intent/tools/ for scripts). Commands run from the repo root. ripgrep and fd skip hidden directories by default; search .intent explicitly or use rg --hidden / fd --hidden.
Intent records
The person has the requirement; the adopting project's agent reads this skill. Finish with a record whose rules and approval state are explicit, not inferred from a green test.
- Read the adopting repository's CONTEXT.md and relevant code/examples. For a new adopter, run
pi-intent init <repo-dir>; otherwise preserve existing records. Read the installed package's SPEC.md for the schema and lifecycle. - Choose a new four-digit id and slug. Write
.intent/records/NNNN-slug.mdusing the installedtemplates/records/0001-change.md. For a retrofit, startdescriptiveand distinguish observed behaviour from proposed rules. For greenfield work, startdraft. - Cite existing terms in CONTEXT.md. Define only terms the record introduces. Give contiguous R1, R2… clauses, concrete input/output examples, freedoms, non-goals and open questions. Done: every clause can be interpreted without guessing and every unresolved decision is visible.
- Ask the person to review the complete record and resolve or explicitly defer questions. Record their explicit approval with
approved-by: <human>andstatus: approved; agents draft and capture human decisions rather than approve themselves. An edited approved meaning returns to draft. Done: approval names the exact reviewed text. - Load
compiled-intent-modelwhen the change has a finite decision worth modeling. Emergent effects, timing or concurrency instead need ordinary tests that name the record's rule. - Feed the approved record into pi-work's marked draft, preserve its clause text as criteria, promote with
work_promote, and decompose with pi-work's authoring/decomposition skills. Follow the ADR-0009 pattern: a model-change node owns changed allowable states; affected implementation nodes depend on it. The link is evidence commands, not a pi-work package dependency or a new schema field.
pi-work handoff
Use the README's worked workspec fragment as the evidence pattern: the model-change node requires node .intent/tools/intent-check.mjs and node .intent/tools/intent-gate.mjs; implementation depends on it and requires node .intent/tools/intent-conform.mjs. Those are kind: command criteria with exit 0 and a nonempty expected success string. Run pi-work's fail-closed work_verify at the explicit worktree and commit; missing, timed-out or stale evidence leaves work unverified. Add --require-coverage if all laws must be exercised.
Done: the record path is a workspec reference, the model dependency is explicit, and each selected check is a criterion whose evidence runs the real command. pi-work does not depend on pi-intent.
04 同仓库更多 Skills
work-execution
Execute a validated pi-work node or wave when you need the ready-set, by-reference work_plan brief, Fabric default, pi-delegate fallback, explicit tree-bound verification, remediation, scope amendments, or a post-integration refactor pass. Use after decomposition and before claiming any node is done.
work-decomposition
Turn a validated pi-work intent into a strict workspec work graph when the work is too large for one bounded worker. Use when assigning criterion homes, dependencies, honest write scopes, open decisions, or optional model-change nodes before planning execution.
work-authoring
Draft a pi-work workspec when an outcome, scope, or proof obligation is still unclear. Use this before turning a conversation, issue, or design into a markdown draft, especially when acceptance criteria need to survive lossless promotion into strict YAML.
intent-conformance
Connect an approved finite Bend model to actual application code with a language-neutral conformance manifest, app-language oracles and a broken-model control. Load when proving implementation parity or diagnosing decision drift.
compiled-intent-model
Author or change a finite Bend model from an approved intent record, review its meaning, obtain human law approval, and produce an offline-verifiable Jev receipt. Load for model-change nodes, not for emergent runtime behaviour.
developing-pi-extension-repos
Keep tests, dependencies, CI reproduction, and coverage reliable across Pi extension repositories. Load when editing, testing, or setting up a worktree in a pi extension repository, when tests pass from source but fail from compiled output (or vice versa), before running `npm install` in a checkout other sessions may be using. For writing extension code itself, load `authoring-pi-extensions`.