| name | project-awareness |
| description | The Project Lead's project-intelligence skill — build a fast, accurate picture of the project (state, active feature, progress, changes, code locations, risks) by retrieving from deterministic sources on demand, never by loading the whole repo. |
Project Awareness
Purpose
Know the project well enough to decide and delegate correctly — its current state
and where things live — by retrieving knowledge on demand. This is the Project
Lead's defining capability; every later step (classify, route, answer, guide)
rests on it.
When to use
At the start of handling any request, and whenever you need current project facts.
Procedure
- Refresh if stale. When the project may have changed since the brain was last built,
run
aspis context — it refreshes the brain and prints the live state in one call (don't
run the updater scripts by hand).
- Live state. Read
.aspis/context/CURRENT_STATE.md (where things stand) and
.aspis/context/RECENT_CHANGES.md (what changed, newest first).
- Locate. Query
.aspis/index/FILE_REGISTRY.yaml to find files and what each
does — read the registry, not the files, to decide where to look.
- Understand without reading bodies. Use
.aspis/index/CODE_MAP.md for a
file's API skeleton (signatures + docstrings) and its imports (how it connects).
For a fresher or narrower view, run
python .aspis/scripts/context/build_code_map.py --scope <path>.
- Working state. Confirm with read-only checks:
git status, git log.
- Deeper exploration. For usages or relationships beyond the map, delegate to
project-explorer and consume its compact findings.
- Stop as soon as you have enough for the task — never load the whole project. Load in
levels per the
context-ladder skill (L1 hot context → L4 only the source the task touches).
Outputs
- Current status and active feature
- Progress and open work
- Where the relevant code lives
- Recent changes and risks that matter to the request
Anti-patterns
- Scanning or globbing the tree instead of using the registry and the explorer.
- Re-deriving state you can read directly from the generated files.
- Loading more than the request needs "just in case".
Growing into it
Semantic search and dependency analysis belong here too; until that tooling
lands, the registry plus project-explorer cover location and relationships.
