setup

Initialize repository directories and policy files for agentic workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/olliecrow/codex --skill setup-olliecrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/olliecrow/codex/tree/main/skills/setup
Command: npx skills add https://github.com/olliecrow/codex --skill setup-olliecrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes essential directory structures and documentation conventions within a repository, ensuring a consistent and organized environment for agentic workflows, especially for new or uninitialized projects.

Core Features & Use Cases

  • Idempotent Setup: Creates or verifies docs/, plan/, AGENTS.md, docs/decisions.md, docs/workflows.md, and .gitignore entries.
  • Convention Enforcement: Enforces best practices for durable documentation, disposable scratch space, and decision capture.
  • Use Case: When starting a new project or onboarding an existing one to an agentic workflow, run this Skill to ensure all necessary directories and policy documents are in place, preventing common organizational pitfalls.

Quick Start

Run the setup skill to initialize the repository's agentic workflow conventions.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I initialize directory structures and documentation conventions for agentic workflows?

To initialize agentic workflows, you need to standardize repository structures by creating `docs/` and `plan/` directories alongside policy files like `AGENTS.md`. This ensures a consistent environment for durable documentation and decision capture.

What files are required for project initialization in an agentic workflow repository?

Project initialization requires policy files such as `AGENTS.md`, `docs/decisions.md`, and `docs/workflows.md`, along with updated `.gitignore` entries. These enforce best practices for disposable scratch space and durable documentation.

Can I run repository setup on existing projects without breaking current configurations?

Yes, you can run repository setup on existing projects because the skill is idempotent. It verifies and applies directory structures and documentation conventions safely without overwriting existing valid configurations.

What is the best way to enforce documentation conventions and capture decisions in a git repository?

The best way to enforce documentation conventions is to bootstrap the repository with standardized `docs/decisions.md` and `docs/workflows.md` files. This establishes a consistent environment for decision capture and durable documentation.

When do I need to configure an `AGENTS.md` file and a `plan/` directory in my repository?

You need to configure an `AGENTS.md` file and a `plan/` directory when starting a new project or onboarding an existing one to agentic workflows. This prevents common organizational pitfalls by establishing disposable scratch space and policies.