trellis-spec-bootstarp

Generate project-specific Trellis coding specs from real codebase analysis.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-spec-bootstarp-hejiajiudeeyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-spec-bootstarp
Source: https://github.com/hejiajiudeeyu/delegated-execution-workspace/tree/main/.agents/skills/trellis-spec-bootstarp
Command: npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-spec-bootstarp-hejiajiudeeyu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams adopting Trellis often end up with generic template specs that do not reflect their actual codebase, giving future agents misleading or empty guidance. This Skill bootstraps or refreshes .trellis/spec/ guidelines grounded in real source files, patterns, and anti-patterns. ## Core Features & Use Cases - Repository Analysis: Uses GitNexus code knowledge graphs, ABCoder UniAST parsing, and direct source reads to map package boundaries, runtime layers, and data flows. - Spec Decomposition & Writing: Splits spec work by package or layer only when the codebase justifies it, then writes concrete rules with real file paths, examples, and anti-patterns. - Placeholder-Free Verification: Runs a final pass to remove template boilerplate, fix index files, and confirm every claim is backed by source or tests. - Use Case: After initializing Trellis in a monorepo, run this Skill to analyze each package and produce tailored .trellis/spec/ coding guides instead of shipping the default templates. ## Quick Start Analyze this repository and write project-specific Trellis spec files under .trellis/spec based on the real code patterns you find.

Frequently Asked Questions about trellis-spec-bootstarp

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

FAQPage Schema
How do I create project-specific Trellis spec files?▼

Initialize Trellis, then analyze the repository with GitNexus, ABCoder, or direct source reads before writing. Fill or reshape files under .trellis/spec with concrete patterns, real file paths, and anti-patterns, and remove any template sections that do not apply.

What tools help analyze a codebase for spec writing?▼

GitNexus builds a code knowledge graph for module boundaries, execution flows, and blast radius via npx gitnexus analyze. ABCoder parses code into UniAST for exact signatures and type shapes, and both can be exposed to the agent through MCP servers.

Does this workflow require a specific AI agent platform?▼

No, the workflow is platform-neutral and uses a single-agent execution model by default. GitNexus and ABCoder are optional tool choices configured through whatever MCP mechanism the host provides, and helper subagents are optional rather than required.

How do I set up GitNexus and ABCoder MCP servers?▼

Run npx gitnexus analyze from the repository root, then register npx -y gitnexus mcp as an MCP server. For ABCoder, install with go install github.com/cloudwego/abcoder@latest, parse each package, and register abcoder mcp ~/abcoder-asts.

How do I verify Trellis specs have no placeholder text?▼

Run grep -R "To be filled\|TODO: fill\|placeholder" .trellis/spec to catch leftover template content. Also check that index.md files match the final spec file set and that every rule links to a real source or test file.