utils

Candango Skills

Candango is a set of skills for taking a feature from repo setup to UAT, with planning, vertical issues, autonomous execution, independent validation, and wrap-up.

Candango depends on selected skills from mattpocock/skills instead of copying them. Candango adds repo-local paths, feature docs, UAT flow, dashboards, and autonomous execution conventions.

Usage

Install Matt Skills First

Install the upstream skills that Candango wrappers call:

npx skills@latest add mattpocock/skills

Select these Matt skills:

• caveman
• grill-with-docs
• to-prd
• to-issues
• tdd

Candango uses them directly:

Candango skill	Matt skill
candango-discover	grill-with-docs
candango-plan	to-prd
candango-issues	to-issues
candango-executor	tdd

Install Skills

Install with skills.sh:

npx skills@latest add lucasbayma/skills

Select the recommended Candango set from candango-skills:

• candango-setup
• candango-discover
• candango-design
• candango-plan
• candango-issues
• candango-uat
• candango-executor
• candango-uat-runner
• candango-wrap-up

Select utility skills from utils:

• check-pr-comments
• fix-pr-checks

Run setup once in each target repo:

Use $candango-setup to configure this repo for autonomous feature delivery.

Quickstart

Use the full flow when you want to deliver a feature end to end:

Use $candango-discover to clarify this feature:

<feature request>

Then use $candango-plan, $candango-issues, $candango-uat,
$candango-executor, $candango-uat-runner, and $candango-wrap-up.
All communication and reports must use $caveman.

For a small feature that is already clear:

Use $candango-plan to plan this small feature:

<feature request>

Then use $candango-issues, $candango-uat, and $candango-executor.

If the feature includes screens, flows, dashboards, apps, forms, or any visual surface, run candango-design before finalizing the plan and issues:

Use $candango-design to locate the design system and coordinate UI work for this feature.
Target surface: <existing codebase | Figma | screenshots | local design artifacts>.

Full Loop

Development Cycle

Executor Cycle

The key point: the executor that implements the work does not validate its own work. It writes code with Matt Pocock's $tdd; another subagent, without the executor's conversation context and without permission to edit, reviews the diff against the issue, plan, and UAT. If validation fails, the main agent turns the report into another TDD round. Manual UAT and final repo validation happen only after that.

Feature Folder

All candango-specific docs and HTML live together:

docs/features/<feature-slug>/

Default contents:

• context.md
• plan.md
• uat.md
• issues.md
• index.html execution dashboard
• state.json execution state
• design/ local UI/design artifacts

index.html and state.json are runtime dashboard files. $candango-wrap-up removes them before PR when they are not needed.

Communication Contract

All user-facing communication and written reports must use $caveman.

This includes:

• planning summaries
• clarification questions
• issue breakdown reports
• UAT reports
• UAT run confirmations
• executor reports
• validator reports
• dashboard history
• final completion reports
• PR descriptions

Skills

candango-setup

Configures the repo for the Candango flow. It discovers or asks which tracker to use, where feature docs live, which command validates the work, where to save the dashboard, how to handle design artifacts, and which rules agents must follow.

It creates local documentation so the other skills do not depend on conversation memory. Run it once per repo, and run it again only when changing tracker, docs convention, or validation process.

candango-discover

Calls Matt Pocock's grill-with-docs with Candango's feature context target: docs/features/<feature-slug>/context.md.

Use it to resolve ambiguous terms, business rules, actors, permissions, happy paths, errors, contracts, UX, rollout, UAT, slicing, final validation, and autonomous-execution readiness.

candango-design