pactile-spec-bootstrap
Bootstrap project-specific Pactile coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .pactile/spec guidelines, analyzing a codebase with whatever code graph or language tooling is already available (or direct source inspection), decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
- License 许可
- AGPL-3.0
- 所属仓库
- blxzer77/pactile
- 最近更新
- 2026-10-01
- Stars
- ★ 16
- Forks
- 0
01 前言 Front Matter
- name
- pactile-spec-bootstrap
- description
- Bootstrap project-specific Pactile coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .pactile/spec guidelines, analyzing a codebase with whatever code graph or language tooling is already available (or direct source inspection), decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.
02 资源文件 4
- 参考文档references/mcp-setup.md1.8 KB
- 参考文档references/repository-analysis.md2.6 KB
- 参考文档references/spec-task-planning.md2.2 KB
- 参考文档references/spec-writing.md2.1 KB
03 SKILL.md 正文
Pactile Spec Bootstrap
Use this skill to create or refresh .pactile/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 Pactile is initialized and inspect the current
.pactile/spec/tree. - Analyze the repository architecture with the best available tools: any code graph or language tooling you already run, plus 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 Pactile spec files | references/spec-writing.md |
| Code graph and MCP setup (tool-neutral) | 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
.pactile/spec/.
Done Criteria
.pactile/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.mdfiles match the final spec file set.- Any required setup or analysis assumptions are documented in the relevant spec or task notes.
04 同仓库更多 Skills
external-review
User-installed review workflow that Pactile may borrow but never delete.
team-skill
Existing team workflow with no Pactile ownership record.
verify-basic
Verify observable behavior at pre-agreed public seams.
observability-local
Record sanitized local execution and decision evidence.
intake-basic
Scope new work before creating an independently acceptable Task.
execute-agent
Implement the approved change inside the frozen write set.