Skill: repo-orientation
Purpose
Fast, low-noise orientation for contributors/agents working in this repository.
When to use
- •At the start of a task.
- •When requirements seem ambiguous.
- •Before proposing architecture changes.
Inputs
- •User task/request.
- •Root docs:
CONCEPT.md,SPEC.md,ARCHITECTURE.md.
Workflow
- •Read root docs in this order: concept -> spec -> architecture.
- •Extract three things: product goal, required APIs, and constraints.
- •Locate candidate implementation paths in
src/and tests intests/. - •Summarize gaps between current code and documented target behavior.
- •Only then propose implementation steps.
Output checklist
- •Goal statement in one sentence.
- •APIs/components impacted.
- •Any dependency on Monty details explicitly called out.