89sooner
6 verified skills6 total stars
implementation-planner
turn grounded repository context into a concrete implementation plan. use when a request asks for impacted modules, change order, api changes, migrations, rollback notes, or implementation risks.
development1
repo-context-finder
collect repository, documentation, issue, and ci evidence for development workflow tasks. use when a request needs related files, existing patterns, dependency context, or grounded evidence.
development1
review-gate
review a proposed change plan or draft implementation summary for missing evidence, regressions, hidden dependencies, compatibility concerns, and readiness. use before returning a final developer recommendation.
development1
test-strategy-generator
generate structured test strategies for a proposed implementation plan. use when a request needs unit tests, integration tests, regression targets, edge cases, or recommended test execution order.
testing1
workflow-orchestrator
orchestrate developer workflow requests across specialist agents. use when a request needs routing, step ordering, evidence preservation, and a final structured response.
development1
requirements-planner
convert natural-language development requests into implementation-ready requirements. use when a feature request, bug report, or refactor idea needs assumptions, acceptance criteria, non-goals, and impacted areas.
development1