agent-repo-setup

Scaffolds repo-local plans/ work tracking and domain documentation conventions for agent skills.

Updated Jan 19, 2023
One-click install
npx skills add https://github.com/inkfin/dotfiles --skill agent-repo-setup-inkfin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-repo-setup
Source: https://github.com/inkfin/dotfiles/tree/main/dot_agents/skills/exact_agent-repo-setup
Command: npx skills add https://github.com/inkfin/dotfiles --skill agent-repo-setup-inkfin

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about agent-repo-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up local markdown ticket tracking for a repo?

Run this Skill once per repository. It creates docs/agents/work-tracking.md defining a plans/<feature-slug>/ layout with spec.md files and numbered ticket files under issues/, including Status and Blocked by fields, with no remote tracker involved.

How to organize domain documentation for AI coding agents?

The Skill writes docs/agents/domain.md describing where CONTEXT.md and ADRs live. Single-context repos use a root CONTEXT.md plus docs/adr/; multi-context monorepos use a CONTEXT-MAP.md pointing at per-context CONTEXT.md files.

Does this skill support monorepos with multiple contexts?

Yes. When exploration detects monorepo signals like pnpm-workspace.yaml or package.json workspaces, it offers a multi-context layout with CONTEXT-MAP.md at the root and per-context CONTEXT.md and docs/adr/ directories.

Can I use this with GitHub Issues or Linear instead of local files?

No. The Skill deliberately configures local markdown tracking under plans/ only, with no GitHub, GitLab, or Linear integration. Specs and tickets live as files in the repository itself.

When should I re-run the agent repo setup skill?

Re-run it only to switch the documentation layout or rebuild conventions from scratch. Routine changes are made by editing docs/agents/*.md directly, and existing Agent skills sections are updated in place rather than duplicated.