By KurtLehnardt
Orchestrator pipeline for Claude Code: plan, review, decompose, parallel workers, critic, merge
Cron supervisor that checks on worker subagents every ~5 minutes, compares their progress against the original plan, and writes NUDGE.md into drifting worktrees. Trigger: babysit, supervise workers, watch agents.
Orchestrate a full implementation pipeline: plan, architect review, executive review, task decomposition, parallel ralph-loop workers, babysit supervisor, critic review, merge. Trigger: build this, implement this, orchestrate this.
Deploy merged code to staging or production, run migrations, verify health, and roll back on failure. Trigger: deploy this, ship it, push to production, go live.
Transform a raw idea into a structured Product Requirements Document with acceptance criteria, tech requirements, and service manifest. Trigger: I have an idea, new app, new feature, build me something, product idea.
Detect required services, check credential vaults, generate .env files, and guide account creation for missing services. Trigger: set up environment, configure project, set up credentials, prepare for build.
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.
Claude Code plugin that implements a full autonomous code factory. Give it an idea — it produces a running application.
/idea → /setup → /build → /test → /deploy → /ship
/status (anytime)
/teardown
| Skill | Purpose |
|---|---|
/idea | Raw idea → structured PRD with acceptance criteria and service manifest |
/setup | Detect required services, check vaults, generate .env, guide account creation |
/build | 7-phase implementation: plan → architect review → exec review → workers → critic → merge |
/test | Generate test suites for existing code without modifying implementation |
/deploy | Deploy to staging/production, run migrations, health check, rollback on failure |
/ship | Go-to-market engine: strategy doc, landing page, free tool, SEO, AEO infrastructure |
/status | Factory dashboard: active builds, scores, blockers, environment health |
/teardown | Clean up worktrees, delete merged branches, archive plans |
/idea — IntakeTakes a raw concept and produces a Product Requirements Document with measurable acceptance criteria, technical requirements, and a service manifest listing every external dependency.
/setup — EnvironmentReads the PRD (or scans the codebase), detects what services are needed, checks your credential vault (1Password CLI, AWS SSM, or .env files), and generates a complete environment configuration. For missing services, it produces a checklist with direct signup links.
/build — ImplementationThe core engine. Runs a 7-phase pipeline with scored quality gates:
/test — CoverageAnalyzes existing code for coverage gaps, prioritizes by risk (auth, payments, data mutations first), and generates comprehensive test suites following existing patterns. Does not modify implementation.
/deploy — ShipPre-flight validation, database migrations, deployment to Vercel/hosting platform, post-deployment health checks, and automatic rollback if health checks fail. Production deploys require human confirmation.
/status — DashboardRead-only snapshot of the factory: active worktrees, review scores, blockers, environment health, backlog status. No subagents dispatched — reads local state directly.
/ship — Go-to-MarketTakes any app (codebase, URL, or description) and produces a tailored marketing strategy + working deliverables. Runs a 5-phase pipeline:
Adapts to product maturity: early-stage gets positioning + strategy, growth-stage gets concrete deliverables and scaling tactics.
/teardown — CleanupRemoves merged worktrees and branches, archives completed plan files, prunes orphaned references. Never deletes unmerged work without human confirmation.
Add to your ~/.claude/settings.json:
{
"enabledPlugins": {
"agentic-tools@C:\\path\\to\\agentic-tools": true
}
}
Or clone and reference:
git clone https://github.com/KurtLehnardt/agentic-tools.git
# Start with an idea
/idea I want a SaaS that converts podcast episodes into blog posts
# Set up the environment
/setup
# Build it
/build
# Add test coverage
/test
# Ship it
/deploy
# Go to market
/ship
# Check on things
/status
# Clean up after merge
/teardown
Default pass threshold is 9.5/10. Edit scoring rules in:
skills/build/references/architect-review-prompt.mdskills/build/references/executive-review-prompt.mdskills/build/references/critic-review-prompt.mdModify skills/build/references/ralph-worker-prompt.md for commit conventions, validation commands, scope rules.
Modify skills/test/references/test-writer-prompt.md for test framework preferences, coverage targets.
npx claudepluginhub kurtlehnardt/agentic-tools --plugin agentic-toolsGive soul to your workflow. 58 AI-powered skills across 17 roles — PM, Dev, Backend, Frontend, QA, UX, Data, Detect, WordPress, Release, Security, DevOps, and Core. Spec-to-ship pipeline: scaffold, implement, test, secure, deploy. Features two-phase workflow with human approval, quality-reviewer agent, token optimization, and continuous improvement via LEARN.md system.
An agent-routed harness for end-to-end software product development
Enhances Claude Code from producing raw code into delivering production-ready systems. 14 specialized agents handle architecture, tested code, security audit, CI/CD, and documentation. Use for building apps/websites/services, adding features, hardening, deployment, testing, review, or architecture design.
Autonomous development methodology: PRD interviews → agent execution → automated review
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams