pillars-verifylisted

# Pillars Verify This skill audits the project's pillar files against the current state of the codebase. It walks each pillar's Context section, checks claims, and flags drift with specific evidence. ## When to use this skill Trigger when the user wants to check whether their pillars are still accurate. Typical requests: - "Verify the pillars." - "Check if my pillars are still accurate." - "Audit the pillars against the codebase." - "Are my pillars out of date?" - "I just did a big refactor; check the pillars." If the user wants to *bootstrap* Pillars, prefer `pillars-init`. If they want to *author or rewrite a specific pillar*, prefer `pillars-author`. ## What this skill produces A structured drift report in the chat (no files written by default). For each pillar: - Claims checked - Drift findings (if any), with the specific evidence in code - Proposed fixes for each finding - Suggested next action After presenting the report, the user can decide which findings to address and (optionally) invoke `pillars-author` to refresh a specific pillar. ## Procedure ### Step 1. Locate the project's scopes and pillars Check the standard locations: ```bash ls AGENTS.md agents/ ``` If either is missing, tell the user: "This project doesn't appear to have Pillars set up. Run `/pillars-init` first." End. Also find nested directories containing both `AGENTS.md` and `agents/`. Verify each scope independently and apply nearest-scope precedence when claims conflict. Read each scop