setup-project

Seeds a repository's agent contract files and fills AGENTS.md project sections.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill setup-project-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-project
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-core/skills/setup-project
Command: npx skills add https://github.com/toderian/project_template --skill setup-project-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repositories need a consistent agent contract (AGENTS.md, CLAUDE.md, settings, ignore blocks) before coding agents can work in them, and that contract drifts out of date whenever the template plugins are updated. This Skill seeds the files with at init, guides the human interview that fills AGENTS.md's Project section, and reconciles routing-table drift after plugin updates. ## Core Features & Use Cases - Repository seeding: Runs at init with flags for tasks, artifacts, workbooks, and repo registries, creating the downstream-owned contract files without overwriting existing content. - Guided AGENTS.md completion: Interviews the user and reads the repo (README, CI config, manifests) to replace TODO-FILL slots with verified commands, domain invariants, and coordination rules. - Update adoption: Follows a desired-state checklist in references/adopting-updates.md to merge new routing-table rows, replace removed skill ids, and re-verify with at doctor. - Use Case: After running at update and restarting the CLI, at doctor reports the routing table is three rows behind the plugin seed; this Skill merges the missing rows while preserving local edits and confirms a clean doctor run. ## Quick Start Ask the agent to set up this repository's agent contract by running at init and filling in the AGENTS.md Project section with you.

Frequently Asked Questions about setup-project

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

FAQPage Schema
How do I set up AGENTS.md for a new repository?

Run `at init` with the flags matching what the project needs, such as --with-tasks or --with-artifacts, then fill the Project section's TODO-FILL slots by interviewing the user and reading the repo. Finish by running `at doctor` to verify.

How do I adopt template updates after updating the plugins?

Follow the desired-state checklist in references/adopting-updates.md: re-run `at init` with flags inferred from existing files, merge missing routing-table rows into AGENTS.md, replace removed skill ids, and commit only the touched files.

Does at init overwrite my existing AGENTS.md or settings?

No, `at init` is idempotent and never overwrites files the repo owns. It reports created, kept, or merged per file, and only generated `.codex/agents/*.toml` role mirrors are refreshed.

Why does at doctor say my routing table is behind the plugin seed?

Because AGENTS.md is downstream-owned, new skills from plugin updates stay unrouted until merged manually. Resolve the seed path with `at seed-path`, insert the missing rows next to their seed neighbours, and keep all local rows and edits.

What should I do when at doctor reports duplicate task IDs?

Never renumber or delete a task to clear the error. Report the collision with both file names and their Created dates, and let the user decide which task survives.