# Agent Skill Design

DuneBoard skills should stay small. Modern models usually know how to plan,
write code, and summarize work; the skill should not repeat generic reasoning
advice.

## Purpose

The skill exists to prevent DuneBoard-specific mistakes:

- bypassing the CLI when a safe command exists
- inventing task IDs
- adding fake dependencies
- closing tasks without acceptance and verification notes
- losing task history while editing Markdown

## Non-goals

- Teaching general project management.
- Teaching general software engineering.
- Encoding a full Scrum, Agile, or Kanban method.
- Splitting into many role skills before real usage proves a need.
- Embedding agent-runtime behavior into the task tracker.

## File Shape

`SKILL.md` is the required Codex skill entrypoint. The skill identity comes
from the containing folder and the YAML frontmatter:

```text
skills/duneboard-agent/SKILL.md
```

## Current Shape

Keep a compact core skill:

```text
skills/duneboard-agent/SKILL.md
```

It covers the operational loop:

1. validate
2. find next work
3. claim or create a task
4. append short notes
5. release, block, or complete
6. validate again

Add workflow skills only when they prevent repeated DuneBoard-specific mistakes:

```text
skills/duneboard-import-ado/SKILL.md
skills/duneboard-organize-local-project/SKILL.md
```

These skills should stay narrow. Project-specific overrides, such as concrete
ADO account names or area paths, belong in the target project, not in DuneBoard.

## When to Add More Skills

Add a separate skill only when the current one becomes too broad or when usage
shows a repeated failure mode. Candidate future skills:

- `duneboard-planning` if feature decomposition needs a stricter protocol
- `duneboard-review` if board consistency review grows beyond validation

Until then, keep the skill pack at these three skills.
