find-features

Discover feature areas in this repository that are missing from <docs-dir>/features/, then create a populated markdown file for each one — following the contract in <docs-dir>/AGENTS_FEATURES.md and the template at <docs-dir>/features/feature-template.md. The agent docs directory (<docs-dir>) is discovered in Phase 1 — it's typically agents-docs/ but setup-agentic-repository may have written it somewhere else.

The Mimas template (setup-agentic-repository) scaffolds an empty <docs-dir>/features/ tree. This skill is the next step — it fills it in.

Phase 1 — Verify prerequisites and locate the docs directory

Confirm the repo has been initialized with the Mimas template, and discover where its agent docs actually live. setup-agentic-repository writes the agent doc tree to agents-docs/ by default (a sibling of any human-maintained docs/), but --docs-dir <dir> can override that (e.g. docs/agents). Don't assume the path; discover it.

1. Read AGENTS.md at the repo root. Every Mimas-generated AGENTS.md lists its docs paths in the first block (<docs-dir>/AGENT_WORKFLOW.md, <docs-dir>/AGENTS_FEATURES.md, etc.) — the directory in those paths is the docs dir for this repo.
2. If AGENTS.md doesn't exist or doesn't reference the contract files, fall back to searching for AGENTS_FEATURES.md directly (find . -maxdepth 3 -name AGENTS_FEATURES.md). The directory containing it is the docs dir.
3. Confirm the files this skill needs are there:
   • <docs-dir>/AGENTS_FEATURES.md — feature documentation contract
   • <docs-dir>/features/feature-template.md — the canonical template
   • <docs-dir>/FEATURES.md — the feature index