一套可重复使用的客服技能，运行着纪律严明、文档驱动的工作流程 用于构建与代理的软件——从想法/问题到经过审查的机密， 随时准备合并变革。技能是项目适应性的：他们会发现并服从 每个仓库都有自己的指南、架构、路线图和运行时的样式文档，所以 同样的工作流程适用于任何堆栈。

它们是普通的Markdown文件（SKILL.md），所以它们可以和任何代理一起工作 读取技能——Claude Code、Cursor、Codex、OpenCode、Cline 和 70+ 其他 — 安装于 skillsCLI（参见 安装）。

docs/中的例子是通用且具说明性的;技能 本身对堆栈和架构都无关。

模型无关安装（[npx skills add gtrabanco/agentic-workflow） 没有技能 model:/effort: 前言——每个技能都只是 继承了你的代理会话已经使用的模型和工作量。 目标是：使用这个工作流程永远不应该局限于某个厂商的模型阵容——你选择模型，技能只是管理整个领域。

里面是什么

Dogfooding 模型（创作）: 仓库会话会消耗来自

Agentic Workflow Skills

A reusable set of agent skills that run a disciplined, doc-driven workflow for building software with agents — from idea/issue to a reviewed, classified, merge-ready change. The skills are project-adaptive: they discover and obey each repository’s own guide, architecture, roadmap and style docs at runtime, so the same workflow works on any stack.

They are plain Markdown (SKILL.md files), so they work with any agent that reads skills — Claude Code, Cursor, Codex, OpenCode, Cline, and 70+ others — installed with the skills CLI (see Install).

The examples in docs/ are generic and illustrative; the skills themselves are stack-agnostic and architecture-agnostic.

The model-agnostic install (npx skills add gtrabanco/agentic-workflow) carries no skill model:/effort: frontmatter — every skill simply inherits whatever model and effort your agent session is already using. The goal: using this workflow should never lock you into one vendor’s model lineup — you pick the model, the skills just run the discipline.

What’s inside

skills/                  28 source skills (13 user-facing + 14 workflow internals + 1 metadata-internal; 27 discoverable — skill-lint is repo-only)
packages/                companion npm packages: @gtrabanco/agentic-workflow-schema (machine contracts)
                         and @gtrabanco/pi-agentic-workflow (one-command install for Pi — see Install)
template/                 the exportable documentation scaffold (the substrate the skills read)
docs/workflow/           the full tutorial (feature flow, issue flow, reference, replication)
docs/features/_TEMPLATE  feature SPEC template + ROADMAP (the planning artifacts skills produce)
docs/fix/                fix SPEC template + index
.github/                 issue + PR templates the workflow expects

Dogfooding model (authoring): repo sessions consume the workflow from the installed release (Pi package / installed plugin), not from the working copy. The committed layout carries no working-copy activation surface. Authoring sessions opt in by creating a local, gitignored mount (ln -sfn ../skills .claude/skills) or by exercising a single working-copy skill via per-session flags (e.g. pi --no-skills --skill skills//SKILL.md).

The skills are the behavior; template/ is the substrate they read (a generic AGENTS.md + documentation map, SPEC/feature/fix templates, and GitHub templates). Scaffold a new project’s way of working with npx degit gtrabanco/agentic-workflow/template my-project — see docs/workflow/REPLICATE.md.

The largest skills use progressive, one-hop loading instead of paying their full