# Repo Tasks

> Build a validated, repo-specific parallel task DAG from an approved LLD and contract.

- Skill: `keyvaluesoftwaresystems/repo-tasks` (Agent Skill)
- Install (CLI): `npx skillmds@latest add keyvaluesoftwaresystems/repo-tasks`
- Raw SKILL.md: https://api.skillmd.com/api/skills/keyvaluesoftwaresystems/repo-tasks/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: keyvaluesoftwaresystems (https://skillmd.com/u/keyvaluesoftwaresystems)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/keyvaluesoftwaresystems/repo-tasks

---


# repo-tasks

Plan only the repository named by the workflow. Read its `AGENTS.md`/`CLAUDE.md`, codebase
map, approved LLD, contract, and the live files needed to verify paths. Do not edit product
code.

Write the requested `tasks.json` in one pass using
`.maestro/engine/schemas/tasks.schema.json`. Set `stack` to the repository name. Split work
into independent slices with disjoint writes; dependencies may only point within a slice.
Every task must list exact reads/writes, a concrete test, applicable standards, and whether
it needs a human gate. Include negative paths, security, compatibility, observability, and
framework-native verification appropriate to the detected repo (web, backend, mobile, or
otherwise). Validate with `python3 .maestro/engine/validate_tasks.py <path>` and correct any
reported error before returning.

## Output contract

Return `task_count` and `slice_count` as short scalar JSON fields on the last line.