grill-with-codebase

Interrogates a task against the actual codebase to shape a concrete implementation plan.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill grill-with-codebase-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-codebase
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/grill-with-codebase
Command: npx skills add https://github.com/danielsuguimoto/skills --skill grill-with-codebase-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague tasks and tickets often lead to plans built on assumptions rather than how the code actually works. This Skill turns an unclear intent into a concrete, file-by-file plan by interviewing you one question at a time, with every question grounded in the real codebase. ## Core Features & Use Cases - Codebase-grounded questioning: Reads affected files, contracts, callers, and tests before asking, and cites file paths and line ranges in every question. - Structured decision coverage: Rotates through scope, existing patterns, data flow, invariants, edge cases, cross-module wiring, and test impact until every decision branch resolves. - Read-only plan output: Produces a confirmed plan with file-by-file changes, migrations, tests, and open risks without modifying any code. - Use Case: You receive a ticket to add soft-delete to a model. The Skill reads the model, its lifecycle hooks, and callers, then grills you on scoping, cascade behavior, and query filtering until a concrete plan emerges. ## Quick Start Ask the agent to grill you about your ticket using the codebase as ground truth until a concrete plan forms.

Frequently Asked Questions about grill-with-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague ticket into a concrete implementation plan?▼

Use an interview-driven approach that asks one question at a time, each with a recommended answer, until scope, data flow, invariants, and test impact are resolved. The output is a file-by-file plan confirmed before any code changes.

How to plan code changes based on existing codebase patterns?▼

Read the affected files, contracts, callers, and tests before deciding anything, and ground every question in what the code does today. When a proposal contradicts an existing pattern or invariant, surface the conflict with the decisive snippet.

Does this planning approach modify my code?▼

No, the skill is strictly read-only. It explores the codebase and records decisions, but only produces a plan; enactment happens separately after you confirm the plan is concrete.

When should I use codebase-grounded planning instead of writing code directly?▼

Use it when a task touches existing modules with invariants, lifecycle hooks, or cross-module wiring that are easy to break. It is less useful for greenfield work with no existing code to ground decisions in.

What topics does the planning interview cover?▼

It covers scope and success criteria, fit with existing patterns, data flow and persistence, invariants and lifecycle, edge cases and failure modes, cross-module wiring, and test impact. Each decision is recorded until all branches resolve.