Agent Skills › fy-agent/fyagent › trellis-spec-bootstrap

trellis-spec-bootstrap

GitHub

基于真实代码库初始化或刷新 .trellis/spec/ 编码规范。通过单智能体工作流分析仓库架构，分解包层级，编写包含具体示例和反模式的文档，确保规范与实际代码一致且无占位符。

.cursor/skills/trellis-spec-bootstrap/SKILL.md fy-agent/fyagent

触发场景

创建或更新项目特定的 Trellis 编码规范分析代码库以生成基于实际结构的规范文档清理或重构现有的 .trellis/spec/ 目录

安装

npx skills add fy-agent/fyagent --skill trellis-spec-bootstrap -g -y

更多选项

不安装直接使用

npx skills use fy-agent/fyagent@trellis-spec-bootstrap

指定 Agent (Claude Code)

npx skills add fy-agent/fyagent --skill trellis-spec-bootstrap -a claude-code -g -y

安装 repo 全部 skill

npx skills add fy-agent/fyagent --all -g -y

预览 repo 内 skill

npx skills add fy-agent/fyagent --list

SKILL.md

Frontmatter

{
    "name": "trellis-spec-bootstrap",
    "description": "Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis\/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package\/layer spec work, and writing real codebase-backed spec docs without placeholder text."
}

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

Confirm Trellis is initialized and inspect the current .trellis/spec/ tree.
Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
Decompose the spec work by package and layer only when that reflects the actual codebase.
Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
Verify that the final specs are internally consistent and contain no template placeholders.

Reference Routing

Need	Read
Repository architecture analysis	references/repository-analysis.md
Spec work decomposition and task planning	references/spec-task-planning.md
Writing high-signal Trellis spec files	references/spec-writing.md
GitNexus and ABCoder MCP setup	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 generic advice. Every important recommendation should point at a real file or repeated local pattern.
Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
Do not write platform-specific instructions unless the target project already standardizes on that platform.
Do not leave placeholder text, empty headings, or copied boilerplate in .trellis/spec/.

Done Criteria

.trellis/spec/ describes the project as it exists now.
Each relevant package or layer has practical coding guidance with real examples.
Non-applicable template sections are removed.
index.md files match the final spec file set.
Any required setup or analysis assumptions are documented in the relevant spec or task notes.