pillars-authorlisted

Draft or revise a specific Pillars pillar file by scanning the relevant code, decisions, and conventions in the current project. Given a pillar name (e.g., data, auth, api, ui, stack, arch), this skill performs targeted archaeology on the codebase, drafts the 8-section pillar body following the Pillars template, includes proper YAML frontmatter, and presents the draft for the user's approval before writing. Use this skill when the user asks to 'author pillar X,' 'draft data.md,' 'create the auth.md pillar,' 'generate pillar from code,' 'fill in pillar X,' 'populate context.md,' or names a specific pillar they want filled in.
hannsxpeter/pillars · ★ 2 · Data & Documents · score 66

Install: claude install-skill hannsxpeter/pillars

# Pillars Author This skill drafts a specific Pillars pillar by scanning the relevant code and presenting a faithful 8-section body for the user to approve. ## When to use this skill Trigger when the user wants a *specific* pillar drafted or revised, with the pillar name given. Typical requests: - "Author the data.md pillar from my codebase." - "Draft auth.md." - "Fill in stack.md." - "Populate context.md from the project description." - "Create the api.md pillar." If the user wants to *scaffold the whole standard*, prefer `pillars-init`. If they want to *check pillars for drift*, prefer `pillars-verify`. ## What this skill produces A complete pillar file at `agents/<pillar>.md` (or sub-pillar at `agents/<parent>/<name>.md`) with: - Correct YAML frontmatter (pillar, status, always_load, covers, triggers, must_read_with, see_also). - 8 body sections (Scope, Context, Decisions, Rules, Workflows, Watchouts, Touchpoints, Gaps). - `status: present` once content is meaningful; `status: stub` only if the user explicitly wants a stub. - Sections populated only where they earn their keep (per Pillars' "earn your keep" principle). ## Procedure ### Step 1. Determine which pillar to author Get the pillar name from the user's request. If ambiguous, ask. Acceptable names are any from the [Pillars catalog](https://github.com/hannsxpeter/pillars/blob/v1.2.2/PILLARS.md): - Always-loaded: `context`, `repo` - Core: `stack`, `arch`, `data`, `api`, `ui`, `auth`, `quality`, `developmen