pillars-initlisted

# Pillars Init This skill bootstraps the [Pillars](https://github.com/hannsxpeter/pillars) standard in a project. It is the recommended entry point: it handles archetype detection, AGENTS.md placement, pillar stub creation, and exclusion list setup in one pass. ## When to use this skill Trigger when the user wants Pillars set up in their current project. Typical requests: - "Set up Pillars on this project." - "Adopt the Pillars standard." - "Initialize Pillars." - "Scaffold AGENTS.md and pillars." - "Install Pillars." If the user wants to *author a specific pillar* from existing code rather than scaffold the whole standard, prefer `pillars-author`. If they want to *check existing pillars* for drift, prefer `pillars-verify`. ## What this skill produces After running, the user's project will contain: ``` <project>/ ├── AGENTS.md # the protocol description, copied from the Pillars repo └── agents/ ├── context.md # stub, status: stub ├── repo.md # stub, status: stub ├── catalog.yaml # offline metadata for absent concerns └── <core-pillars>.md # stubs for Tier 1 pillars that apply to this archetype ``` With archetype-appropriate `excluded:` entries in AGENTS.md. ## Procedure Follow these steps in order. Each step has a specific output the next step depends on. ### Step 0. Confirm intent and check for existing adoption Before scaffolding anything, check whether the project already has Pillars in place. ```bash ls AGENT