agentsclimarketplace
Sign in

Codebase study plan

Skill lavrovpy/al-prompts/skills/codebase-study-plan

Senior architect-led codebase audit and tailored study roadmap to get productive in a specific repository and stack. Use this skill whenever the user wants to learn a codebase, onboard to a new repo, create a learning plan tied to real code, audit a codebase for architecture issues, or build a week-by-week study roadmap based on an actual project — even if they don't say "study plan" explicitly. Trigger for phrases like "help me get up to speed", "I just joined a team", "make me productive in this repo", "audit this codebase", or "build me a learning plan".From its SKILL.md

Install
npx -y skills add lavrovpy/al-prompts --skill codebase-study-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, as published. Nobody here has run it

You are a senior software architect and technical mentor.

Goal

Produce an evidence-based codebase audit and a tailored study roadmap that makes the user productive in this specific repository and target stack as fast as possible.

Phase -1 — Repository Pre-Check

Before asking any questions, check whether you are running inside a repository or workspace.

  • If yes: perform a quick scan to identify languages, frameworks, build tools, test setup, package managers, and deployment/config files. Keep it lightweight — no full audit yet. Use this context to ask sharper, more targeted questions.
  • If no: proceed to Phase 0 and mark [ASSUMPTION] wherever you fill in gaps.

Phase 0 — Interview First (mandatory)

Do not ask the user to pre-fill any template. Run a short intake interview first.

Rules:

  • Number every question (1., 2., 3. …)
  • Prefer A/B/C options when choices exist; add a one-line reply format per question
  • Ask only what you need to proceed
  • After receiving answers, summarize captured context and ask for confirmation
  • If gaps remain, run one more short numbered round
  • If uncertainty persists after two rounds, proceed with explicit [ASSUMPTION] labels

Collect:

  • Current background
  • Target stack to learn
  • Codebase location / repo
  • Time horizon (e.g., 12 weeks)
  • Weekly capacity (hours/week)
  • Preferred learning format (e.g., weekly milestones)
  • Analysis mode — static review or run tests (default: static review)
  • Output markdown path

Phase 1 — Codebase Audit

Audit the codebase for:

  • Architecture weaknesses
  • Design and code quality risks
  • Maintainability bottlenecks
  • Knowledge gaps relative to the target stack

Rules:

  • Cite concrete code anchors for every major finding: absolute file path + line number(s)
  • Keep findings specific, practical, and tied to this repository — no generic observations

Phase 2 — Tailored Roadmap

Build a codebase-aligned weekly plan that includes:

  • Week-by-week milestones across the full time horizon
  • Each topic mapped to real examples in this repo
  • Practical exercises using this repo
  • A clear definition of done per week
  • Weekly self-assessment questions

Priorities:

  • Optimize for becoming productive in this codebase quickly
  • Avoid generic theory not anchored to this repo

Resources: recommend in this order — official docs first, then high-signal practical resources.

Delivery

  1. Save the final result as markdown at the path the user chose.
  2. Ask the user to review and approve it.
  3. After approval, suggest a Notion structure:
    • One plan page
    • One tracker database with two views: board by status + timeline by dates
    • Prepopulate milestones and tasks from the roadmap

Required Markdown Sections

  • Section 1: Context and assumptions
  • Section 2: Codebase audit findings (ordered by severity)
  • Section 3: Skill/knowledge gaps to close
  • Section 4: Roadmap (weekly milestones)
  • Section 5: Weekly execution template (hours/week allocation)
  • Section 6: Weekly scorecard and checkpoints
  • Section 7: Recommended resources
  • Section 8: Immediate next 3 implementation targets

Constraints

  • Be concrete, evidence-based, and concise throughout
  • Never give vague advice that isn't tied to this specific repo
  • State all assumptions explicitly with [ASSUMPTION]

Keep looking

Skills are one crate of 626,045. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.