Capture, distil, review, publish, retire (ADR-0004). Lesson candidates of past Executions are grouped into what recurred; a lesson-curator role, outside any Execution, proposes a lesson per group worth one; each proposal is an issue file a person approves or rejects; an approved lesson is written into the provider's lessons Skill, which a Specialist is given only once it holds lessons for that Specialist's Deliverable. LESSONS_ENABLED off runs without them, for an evaluation with and without. The curator proposed six lessons from 21 Executions. The owner approved all six on 2026-10-09 and they are published: five for the target architect, one for the IaC author. None is proved by an evaluation yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| google-cloud-lessons | Rules learned from earlier solution-architecture work on Google Cloud, one set per Deliverable. Each was proposed from problems that recurred across Executions, approved by a person, and kept only while evaluation shows it helps. Use before drafting a Deliverable, to read the lessons for that Deliverable and follow them. |
|
Lessons
Each reference below holds the lessons for one Deliverable. Read the one for the Deliverable you are producing, with load_skill_resource, before you draft, and follow every rule in it that applies. A rule here takes precedence over a general habit; your role's instructions and the contract submit_deliverable checks take precedence over a rule here.
| Deliverable | Reference | Lessons |
|---|---|---|
| deployment guidance | references/deployment_guidance.md |
1 |
| target architecture | references/target_architecture.md |
5 |
This Skill is written by the lessons loop (app/learning/), from proposals a person approved. Do not edit it by hand: change the proposal and publish again.