repo-intake-and-plan
SkillFiles & storageYour AI can study a code repository and come back with a plan for working on it. Instead of jumping straight into changes, it first looks through the code and lays out the work ahead. You get a clear starting point before anything is touched.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding the skill, point your AI at the repository you want to work on and ask it to analyze the code and draft a plan. Review the plan it produces before any changes are made.
Then ask your AI: use the repo-intake-and-plan skill
What your AI can do with it
- Analyze a code repository
- Produce a plan for working on that code
- Understand a codebase before making changes
- Get a clear picture of the work ahead before starting
What this skill tells your AI
The instructions your AI receives, as published by lllllllama/rigorpilot-skills in skills/repo-intake-and-plan/SKILL.md and read by ahel’s review.
Use this as the Rigor Intake helper. The installed slug remains
repo-intake-and-plan for compatibility.
When to apply
- At the beginning of README-first reproduction work.
- When the main skill needs a fast map of repo structure and documented commands.
- When inference, evaluation, and training candidates must be classified conservatively.
- When the user explicitly wants to inspect the repo first and not run anything yet.
When not to apply
- When execution has already started and the task is now about running commands or writing outputs.
- When the target is not a repository-backed reproduction task.
- When the user only wants paper interpretation without repo inspection.
- When the user already has a selected documented command and only needs setup or execution.
Clear boundaries
- This skill scans and plans.
- This skill is helper-tier and should usually be orchestrator-invoked.
- It does not install environments.
- It does not prepare large assets.
- It does not execute substantive reproduction commands.
- It does not decide high-risk patching.
Input expectations
- Target repository path.
- Access to README and common project files if present.
- Optional user hints about desired priority, such as inference-first.
Output expectations
- concise repo structure summary
- documented command inventory
- inferred candidate categories: inference, evaluation, training, other
- minimum trustworthy reproduction recommendation
- notable ambiguity or risk list
Notes
Use references/repo-scan-rules.md and helper scripts under scripts/.
Signals
- GitHub stars
- 487
- Forks
- 17
- Last commit
- Sep 2026
- Installs
- 450k installs
Advanced
- Catalog kind
- skill
- Gateway key
repo-intake-and-plan- Source
- github.com/lllllllama/rigorpilot-skills