/readiness-report slash command #786
Description
What feature would you like to see?
readiness-report feature
A slash command that evaluates how well-prepared a repository is for AI agents to work autonomously.
Why?
As AI agents become more capable, developers need to know if their repo has the tooling, documentation, and processes needed for agents to work effectively. This helps identify gaps and track improvement over time.
How it works
Evaluates the repo against an Autonomy Maturity Model with 5 levels:
Level Requirements
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1 Functional README, linter, type checker, tests
2 Documented AGENTS.md, devcontainer, pre-commit hooks
3 Standardized Integration tests, secret scanning, metrics
4 Optimized CI/CD, coverage tracking, fast feedback
5 Autonomous Analytics, experiment infrastructure
To unlock each level, you need 80% of the previous level's criteria.
Example usage
/readiness-report
Level Achieved: Level 2: Documented
Level 1: 7/7 (100%) ✅
Level 2: 4/5 (80%) ✅
Level 3: 1/6 (16%)
Style & Validation:
- Linter: 1/1 ✅
- Type checker: 1/1 ✅
- Pre-commit hooks: 0/1 ❌
Action items:
- Add pre-commit hooks (husky/lint-staged)
- Enable branch protection
What it checks
9 technical pillars: Style/Validation, Build, Testing, Documentation, Dev Environment, Observability, Security, Task Discovery, and Product/Experimentation.
Implementation
• Purely static analysis (no code execution)
• Works with monorepos (detects Turborepo, Nx, etc.)
• Supports JS/TS, Python, Rust, Go, Java, and more
• Markdown and JSON output formats
I've built a working version as a skill - happy to contribute it!
Additional information
No response