trellis-spec-bootstraplisted

# Trellis Spec Bootstrap Use this skill to create or refresh `.trellis/spec/` guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand. ## Workflow 1. Confirm Trellis is initialized and inspect the current `.trellis/spec/` tree. 2. Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads. 3. Decompose the spec work by package and layer only when that reflects the actual codebase. 4. Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project. 5. Verify that the final specs are internally consistent and contain no template placeholders. ## Reference Routing | Need | Read | |------|------| | Repository architecture analysis | [references/repository-analysis.md](references/repository-analysis.md) | | Spec work decomposition and task planning | [references/spec-task-planning.md](references/spec-task-planning.md) | | Writing high-signal Trellis spec files | [references/spec-writing.md](references/spec-writing.md) | | GitNexus and ABCoder MCP setup | [references/mcp-setup.md](references/mcp-setup.md) | ## Operating Rules - Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it. - Prefer source-backed rules over g