Amby analyze
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-analyzeAssembled 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
Cross-check spec, plan, and tasks for coverage, consistency, and dependency-graph health.
SKILL.md
1.1 KB, as published. Nobody here has run it
Analyze feature the user's request that followed this skill invocation (default: the current feature) for consistency. Read-only — report, don't edit.
Check and report:
- Coverage: every
FR-###/US-#in the spec is addressed by the plan and has at least one task; every task maps to a realUS-#. List orphans and gaps. - Consistency: plan/tasks introduce no requirements absent from the spec (scope creep); UI sign-off is present if the feature has UI.
- Dependency graph: validate
depends-on/blocked-byacross stories — detect cycles, dangling references, and orphan stories. Report which stories are currently blocked vs buildable now. - Clarity: any remaining
[NEEDS CLARIFICATION]markers.
Output a short, structured report (tables/bullets). Prefer machine-checkable facts over prose. Do not modify any file.