himkt/cafleet/cafleet-design-doc
Claude Code and agent skill by himkt/cafleet
- community
Checking that the SKILL.md file is still in the repository.
Use when the user asks to create a design doc, design document, specification, or technical spec (create workflow → Director/Drafter/Reviewer team); or to implement or execute a design doc (execute workflow → TDD or Programmer-only team). Also the standardized format spec — consult the template and guidelines when editing a design doc. Always invoke this skill and route into the matching workflow, orchestrated as a CAFleet team. Teammates in member teams load the core and assigned references through their backend's supported skill-loader without starting another team.
Install
npx vskill@latest install himkt/cafleet/cafleet-design-docSKILL.md
Design Document Skill (CAFleet Edition)
This skill is the umbrella for the full design-document lifecycle: the standardized format spec plus the CAFleet-native orchestration workflows linked in Dispatch. It is a dispatcher — consult a reference page for the format, or route to the matching workflow body to run a team.
Assigned teammates load this skill through the executing backend's supported loader and continue the existing assigned workflow; loading this umbrella as a member creates no second team. Main-session user requests follow Dispatch below.
Required reading
Before routing into a workflow or consulting a reference page, Read your overlay — it is row #1 below. Identify your coding agent first: your spawn prompt's CODING AGENT: line names it; a standalone / main-session reader uses its own identity.
Load-bearing — Read before acting:
| # | Read | What you lose if you skip it | |
|---|---|---|---|
| 1 | your overlay section `../cafleet/reference/coding-agents.md#<name>` — read and resolve it (see Resolve your overlay in the cafleet SKILL.md) | you skip resolution — the failure modes Resolve your overlay closes, e.g. a literal {decision_surface} emitted unresolved |
On-demand — consult directly (no team), only when the task needs it:
| Read | When | |
|---|---|---|
| reference/guidelines.md | you are writing or checking a doc against the standard structure (the template opens the page), or need section guidelines, quality standards, or formatting rules | |
| reference/coordination.md | you need the inter-member verb + pointer + COMMENT(role) schema |
Each workflow body linked in Dispatch carries its own Required-reading block for the team it runs — BASE resolution, supervision, and coordination are gated there, not on this dispatch surface.
Dispatch
For a main-session user request matching a scenario below, invoke this skill and run the linked workflow as a full CAFleet team — proactively, the moment the request matches, without waiting for the user to say "use cafleet".
Routing into a workflow means executing its entire orchestration. The Director registers its current session with cafleet fleet create, spawns the role team, receives each ready and drives the workflow’s review/revision rounds through approval. The Director retains native inbox reception for the fleet's lifetime, ending it only through fleet deletion; the linked workflow body owns its phase gates.
| When the user wants to… | Invoke this skill and run | |
|---|---|---|
| Create a design doc / specification / technical spec | the create workflow (create/create.md) — Director/Drafter/Reviewer team | |
| Implement / execute a design doc | the execute workflow (execute/execute.md) — TDD or Programmer-only team |
Member startup
Every design-doc team member opens its authoritative role first and follows the CAFleet reader and ready rule. Complete these reads in order before the first substantive assignment, using your CODING AGENT: identity.
| # | Read | Timing and responsibility | |
|---|---|---|---|
| 1 | Your backend section in coding-agents.md | Resolve your Runtime bindings, supported skill loader and bound notes. | |
| 2 | CAFleet core and member role | Startup identity, ready, broker commands, member authority and shutdown. | |
| 3 | BASE | Before task work: inherited BASE, guarded writes and missing-line status. | |
| 4 | This core and guidelines | Load the assigned workflow's format and role references before document work; retain your role's scope. | |
| 5 | Coordination | Before payloads, markers and work/status messages. |
Read command routing before routing a command your harness denied. Apply supplied host-rule equivalents where optional files are absent; route an essential unknown prerequisite to the Director before dependent work.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/cafleet-design-doc/SKILL.md
Popularity
- Repository stars
- 51
- Repository forks
- 4
- 7-day trend score
- 20
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/himkt/cafleet/cafleet-design-doc)