cafleet-design-doc

Solid

Use when the user asks to create a design doc, design document, specification, or technical spec (create workflow → Director/Drafter/Reviewer team); to validate, review, or interview an existing design doc through multi-round Q&A (interview workflow); or to implement or execute a design doc (execute workflow → TDD 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 this skill by its name cafleet-design-doc via their backend's skill-loader.

Code & Development 43 stars 4 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Design Document Skill (CAFleet Edition) This skill is the umbrella for the full design-document lifecycle: the standardized **format spec** plus three CAFleet-native **orchestration workflows** (create, validate/interview, implement/execute). It is a dispatcher — consult a reference page for the format, or route to the matching workflow body to run a team. **Teammates in member teams** must always load this skill by its name `cafleet-design-doc` via their backend's skill-loader — never by reading the skill files directly. ## 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 [`../cafleet/reference/coding-agent/<name>-overlay.md`](../cafleet/reference/coding-agent/) — read **and resolve** it (see *Resolve your overlay* in the cafleet `SKILL.md`) | you skip resolution — you emit a literal `{monitor_model}` / `{decision_surface}` in the workflow you route into, **or** guess a wrong/default value, **or** ignore a backend note (codex has no harness task list) | **On-demand — consult directly (no team), only when the task needs it:** | Read | When | |------|------| | [reference/guidelines.md](reference/guidelines.md) | y...

Details

Author
himkt
Repository
himkt/cafleet
Created
4 months ago
Last Updated
3 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

cafleet-research

Use when the user asks to research a topic or create a multi-source research report (report workflow → Director/Manager/Researcher team writing to researches/<topic>/); to build a presentation, slide deck, or reading transcript from a report (presentation workflow); to create a chart, plot, graph, figure, or data visualization (visualization reference); or to author slides with the custom Slidev theme (slidev reference). Always invoke this skill and route into the matching workflow, orchestrated as a CAFleet team. Members in member teams load this skill by its name cafleet-research via their backend's skill-loader.

43 Updated 3 days ago
himkt
AI & Automation Solid

clean-docs

Clean up the repository's docs, comments, rules, and tests as a CAFleet team of disjoint-slice scanner members gated by a reviewer — exactly one workflow per run. Use the residue workflow when the user asks to clean up historical narration or historical residue, remove deprecation notes / "this replaces X" / "renamed from Y" / "previously … now …" prose, drop design-number provenance citations, or delete removal-sentinel tests. Use the affirmative workflow when the user asks to run an affirmative-writing sweep, fix prohibition-only rule sections, pair prohibitions with affirmatives, remove meaningless fallbacks, or make code fail fast. Use the simplification workflow when the user asks to simplify the docs or comments, tighten verbose prose, de-duplicate documentation, or remove redundant comments. Nothing is applied before the reviewer approves the merged run artifact. Members load this skill by its name clean-docs via their backend's skill-loader.

43 Updated 3 days ago
himkt
API & Backend Solid

skill-author

Teach an author how to integrate the CAFleet-orchestrated team pattern into a new skill they are writing. Auto-load when the author intends to create a new CAFleet-orchestrated skill, write a skill that spawns cafleet members, add a Director/Member team skill, design a multi-agent broker-coordinated skill, build a CAFleet-team-driven skill, or write a skill that uses `cafleet member create`. This skill is project-local to the cafleet repo and is fully self-contained — no `cafleet` `reference/base-dir.md` cross-reference is required to follow the guide.

43 Updated 3 days ago
himkt