By durutheguru
Autonomous full-stack development agent that implements entire technical specifications with 99%+ test coverage. Use when you have a complete MVP_technical_spec.md or technical_spec.md ready for implementation.
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub durutheguru/Claude-Plugins --plugin engineerQuality Assurance agent that generates test cases (specifications), executes existing tests, analyzes coverage gaps, and produces structured reports. Identifies bugs and missing test coverage for engineer to address.
Battle-tested CTO providing strategic technical leadership. Manages priorities, technical debt, architecture decisions, testing strategy, and business metrics through `.notes/` folder. Use `/cto:think` to process brain dumps into structured notes.
Multi-perspective quality review for product_spec.md files. Use after generating a PRD to ensure it meets production-ready standards through skeptical engineer, user advocate, business strategist, QA, and clarity editor lenses.
Collaborative brainstorming facilitator that develops raw ideas into well-defined concepts. Use when user has an idea to explore, wants to think through a concept, or needs help clarifying a fuzzy vision before implementation.
Transform brainstorm.md into a comprehensive Product Specification Document. Use when user has a brainstorm file ready and wants to create a formal product spec with features, user flows, technical requirements, and release strategy.
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Provider-agnostic skills for autonomous product development: spec, task, implement, test, review, and summarize changes.
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
Context-driven development framework that enables structured lifecycle for software projects: Context → Spec & Plan → Implement
Specification-driven development workflow: specify → plan → tasks → implement
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation