Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lllllllama avatar

Repo Intake And Plan

  • 11 installs
  • 512 repo stars
  • Updated July 26, 2026
  • lllllllama/ai-research-workflow-skills

This is a copy of repo-intake-and-plan by lllllllama - installs and ranking accrue to the original listing.

Helps with productivity & planning tasks.

About

repo-intake-and-plan is a Claude Code skill for productivity & planning. It helps solo builders move faster with AI-assisted development.

  • repo-intake-and-plan
  • Productivity & Planning
  • AI-coding skill

Repo Intake And Plan by the numbers

  • 11 all-time installs (skills.sh)
  • Data as of Aug 3, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lllllllama/ai-research-workflow-skills --skill repo-intake-and-plan

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs11
repo stars512
Last updatedJuly 26, 2026
Repositorylllllllama/ai-research-workflow-skills

What it does

Helps with productivity & planning tasks.

Files

SKILL.mdMarkdownGitHub ↗

repo-intake-and-plan

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/.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.