Robin11
Community@chenziyang110
Robin11 maintains a Spec Kit Plus skill registry spanning multi-language test generation, spec-driven development commands, debugging, and code review.
Agent Skills by Robin11
Showing 68 vetted skills indexed across 2 GitHub repositories.
chenziyang110sp-prd-scan
Scans existing repositories to produce reconstruction-grade evidence packages for PRD compilation.
chenziyang110sp-map-scan
Builds a value-weighted evidence baseline of a brownfield codebase for graph reconstruction.
chenziyang110sp-constitution
Creates and amends the project constitution governing spec-kit specification and planning workflows.
chenziyang110sp-map-build
Rebuilds the schema v5 SQLite project cognition runtime from validated scan evidence.
chenziyang110spec-kit-ui-design
Enforces design-system alignment and evidence requirements for UI work in Spec Kit projects.
chenziyang110sp-research
Routes sp-research invocations to the sp-deep-research feasibility gate workflow.
chenziyang110sp-accept
Guides humans through step-by-step product acceptance of completed spec-kit features.
chenziyang110sp-implement-teams
Execute spec-kit implementation tasks through Claude Code Agent Teams with shared task ledgers.
chenziyang110test-driven-development
Enforces writing failing tests before production code using red-green-refactor cycles.
chenziyang110sp-clarify
Strengthens existing specification packages by closing planning-critical gaps before planning.
chenziyang110sp-discussion
Matures rough ideas into validated requirement contracts before formal specification.
chenziyang110sp-design
Generates and audits a DESIGN.md design-system contract before UI implementation work.
chenziyang110sp-debug
Investigate bugs through a resumable evidence-driven debug session workflow.
chenziyang110sp-taskstoissues
Converts tasks.md task plans into dependency-aware GitHub issues.
chenziyang110sp-prd
Routes deprecated sp-prd invocations to the canonical sp-prd-scan and sp-prd-build workflow.
chenziyang110sp-explain
Explains spec-kit stage artifacts and project cognition state in plain language.
chenziyang110sp-fast
Executes trivial low-risk code changes directly without entering the full specify-plan workflow.
chenziyang110sp-prd-build
Compiles a validated scan reconstruction package into a delivery-grade PRD suite.
chenziyang110sp-integrate
Runs integration prechecks and closeout for completed feature lanes before mainline merge.
chenziyang110sp-auto
Routes to the next Spec Kit Plus workflow step based on repository state.
chenziyang110sp-plan
Generates implementation planning artifacts from a planning-ready spec contract in spec-kit projects.
chenziyang110spec-kit-discussion-handoff-review
Review agent-only discussion handoff contracts before downstream specification consumption.
chenziyang110sp-specify
Generates planning-ready specification packages from feature requests through guided requirement discovery.
chenziyang110sp-map-update
Incrementally refresh a query-backed project cognition baseline from git diffs and user corrections.
Frequently Asked Questions About Robin11
FAQPage SchemaWhat tasks can I accomplish with Robin11's skill registry?▼
You can generate and fix tests in Python, Java, Kotlin, C, C++, Go, Rust, Ruby, PHP, Swift, Dart, Zig, and JavaScript/TypeScript, enforce TDD red-green cycles, run Playwright end-to-end checks, perform systematic debugging, produce severity-labeled code reviews, and execute the full Spec Kit Plus specify-plan-tasks-implement lifecycle.
Who is the target audience for these skills?▼
Software engineers, QA engineers, and technical leads working in spec-driven repositories who need language-specific test scaffolding, disciplined debugging with evidence capture, PR review feedback, and structured feature delivery from specification through human acceptance.
What are the prerequisites for running these skills?▼
Nearly every skill requires a Spec Kit project structure containing a .specify/ directory. Language testing skills additionally assume the relevant ecosystem toolchain such as pytest, JUnit 5, GoogleTest/CMake, cargo, or RSpec, while deep-research uses firecrawl and exa MCPs.
How do the sp-* command skills fit together in practice?▼
Start with sp-discussion or sp-specify for requirements, refine via sp-clarify and sp-checklist, plan with sp-plan and sp-tasks, implement through sp-implement or parallel subagent dispatch, then close out with sp-review, sp-integrate, and sp-accept. sp-auto resumes the recommended next step from repository state.
Are these skills open source and what do they cost?▼
The skills are published as public GitHub repositories under the chenziyang110 account with metadata attributing github-spec-kit template sources. No licensing fees or paid tiers are indicated in the manifest; they are freely inspectable skill definitions.