agents-best-practices vs pilot-shell
agents-best-practices: A provider-neutral Agent Skill library for designing, auditing, and refactoring agentic harnesses compatible with Codex and Claude Code. It covers the full control plane of an agent runtime: typed tool design, permission checks, context management, memory, and observability. Targeted at developers building production-ready agent systems across any domain or AI provider.; pilot-shell: Pilot Shell enhances Claude Code with structured workflows for spec-driven development, efficient bug fixes, and product requirement generation. It integrates quality gates, preserves context, and optimizes token usage, enabling engineers to produce consistent, production-grade code.
TL;DR
Generate MVP agent harness blueprints for any business domain (CRM, ops, finance, healthcare)
- You use Claude Code and want `/spec` to replace plan mode with discuss, plan, approve, TDD, verify.
- You want separate flows for bugs (`/fix`) and requirements (`/prd`).
- You want teammates to review a spec through a shared link.
- You use an agent other than Claude Code: it only works on top of Claude Code.
- You need clear licence terms: GitHub does not detect a licence, so confirm before using it at work.
- Most of your tasks are small: a full spec flow is heavier than plain Claude Code.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.