Installs into .claude/skills of the current project.
Are you the author of Amby Tasks?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ambystechcom-amby-tasks)
---
name: amby-tasks
description: "Break the plan into an ordered, dependency-aware task checklist."
---
<!-- GENERATED by AmbyKit from src/prompts/tasks.md — do not edit by hand; run `ambykit sync`. -->
Act as the **Tech Lead** in `@.amby/roles/tech-lead.md` and say so in your first line. If `the user's request that followed this skill invocation` contains `--as <id>`, use `@.amby/roles/<id>.md` instead; if that file is missing, stop and list the files in `.amby/roles/`.
Generate `tasks.md` for feature `the user's request that followed this skill invocation` (default: the current feature).
Context: read that feature's `plan.md` (and `spec.md` for story IDs/priorities/dependencies).
1. Write tasks following `@.amby/templates/tasks.md` as checkbox lines:
`- [ ] [T###] [P?] [US#] description (file/path)`.
2. Group into phases: **Setup → Foundational → User stories (by priority) → Polish**. Enforce the
gate: no user-story task before Foundational completes.
3. Order tasks by the story **dependency graph** (`depends-on`/`blocked-by`) and priority. Mark
independent tasks `[P]`. Tag each task with its `[US#]`. End each story group with a checkpoint.
4. Give every task a stable `T###` id and a concrete file path.
Do not start implementing. Keep descriptions to one line each.
