Curate Knowledge
Add developer-authored annotations to the knowledge base.
When NOT To Use
- Knowledge derivable from the code itself (use
gauntlet:extract) - The DSA problem bank (use
gauntlet:gauntlet-curate)
Steps
- Identify the module to annotate
- Ask for the concept (key insight or rule)
- Ask for the why (rationale, history, context)
- Generate YAML annotation file
- Save to
.gauntlet/annotations/<slug>.yaml - Confirm saved and will be included in future challenges
Exit Criteria
- A YAML file exists at
.gauntlet/annotations/<slug>.yamlafter the skill completes, where<slug>is derived from the annotated module and concept - The YAML file contains at minimum a
conceptfield (key insight or rule) and awhyfield (rationale/history/context) - Confirmation message states the annotation will be included
in future challenges, indicating it is on the discovery path
for
gauntlet:extract - Annotation does not duplicate an existing entry under the same slug (checked before saving)