Amby tasks
Spec-Driven Development framework that helps AI coding assistants build better software — author your specs, user stories, UI design, plans and tasks once, and emit native config for Claude Code, OpenCode, GitHub Copilot, Cursor, Antigravity and more.
npx -y skills add ambystechcom/AmbyKit --skill amby-tasksAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Break the plan into an ordered, dependency-aware task checklist.
SKILL.md
1.0 KB, as published. Nobody here has run it
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).
- Write tasks following
@.amby/templates/tasks.mdas checkbox lines:- [ ] [T###] [P?] [US#] description (file/path). - Group into phases: Setup → Foundational → User stories (by priority) → Polish. Enforce the gate: no user-story task before Foundational completes.
- 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. - Give every task a stable
T###id and a concrete file path.
Do not start implementing. Keep descriptions to one line each.