What problem does it solve? Repositories lack a consistent convention for where agent-generated specs, tickets, and domain documentation live, causing skills like to-spec and to-tickets to scatter files or rely on remote trackers. This Skill writes the repo-local conventions once so every subsequent agent workflow knows where to read and write. ## Core Features & Use Cases - Local work tracking setup: Establishes plans/<feature-slug>/ directories holding spec.md files and numbered ticket files under issues/, with status and blocking metadata, replacing GitHub/GitLab/Linear trackers. - Domain docs layout: Configures single-context (CONTEXT.md plus docs/adr/) or multi-context (CONTEXT-MAP.md plus per-context CONTEXT.md) documentation structures based on detected monorepo signals. - Agent entry-point integration: Adds or updates an Agent skills section in an existing CLAUDE.md or AGENTS.md so other skills discover the conventions. - Use Case: Before running to-spec on a new repository, invoke this Skill to create docs/agents/work-tracking.md and docs/agents/domain.md, then all later specs and tickets land consistently under plans/. ## Quick Start Ask the agent to run the agent-repo-setup skill to configure plans/ tracking and domain docs for this repository.