Magnus HedemarkandGitHub
cff17c5974
* fix: SkillOpt Epoch 1 — forward-deployed-engineering optimization Inline the nine-stage contract table into SKILL.md (required question, minimum output, stop condition per stage) with template links and the entry-evidence rule; dedup the stage table out of references/lifecycle-and-artifacts.md into a pointer. Name agent-evals-and-observability and production-readiness inline in the applied-AI release gate (loading protocol step 5). Validated: 2/2 held-out edits accepted (non-regression, all-pass baseline), repo validators green (validate-skills, validate-skill-quality, validate-bundles, validate-evals). * fix: SkillOpt Epoch 2 — forward-deployed-engineering optimization Add a 'Where to enter the lifecycle' table (existing state -> entry stage, with the neckbeard route for bounded changes) and the entry-evidence rule for mid-stream joins. Replace the flat 'When not to use' list with a proactive Scenario | Reach for | Why routing table covering the six boundary routes. Validated: 2/2 held-out edits accepted (non-regression, all-pass baseline) plus a regression probe on epistemic labels; repo validators green. * fix: SkillOpt Epoch 3 — forward-deployed-engineering optimization Add references/worked-example-engagement.md, a fully synthetic depth calibration artifact showing the charter, evidence-labeled ledger, stage handoff, evaluation and release decision, adoption scorecard, outcome measurement record, and productization record for one engagement. Add a File map row, enumerate the templates row (surfacing engagement-status), and add a depth-calibration pointer in the Lifecycle section. Validated: 2/2 held-out edits accepted (non-regression, all-pass baseline); repo validators green; sanitization scan clean (no private identifiers).
1.1 KiB
Lifecycle and Artifacts
The lifecycle is a continuity contract, not a claim about industry standard practice. The nine-stage contract — required question, minimum output, and stop condition per stage — lives in SKILL.md and is the single source of truth for stage expectations.
Every stage records entry evidence, the artifact produced, the accountable decision maker, unresolved unknowns, and the next handoff in the shared records below.
Shared record fields
For every stage record: date, stage, accountable lead, decision authority, entry evidence, work performed, source/evidence label, observed result, unknowns, risks, decision rule, decision, commitment, owner, due date, and next handoff. A stopped engagement remains a valid output if the stop reason and learning are preserved.
Use the canonical stage-handoff record for those fields. Maintain engagement status as the concise current-state view; it supplements rather than replaces the stage evidence and handoff record.