skills.rest
ladislas
ladislasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pac-grill-with-docs

Grill issue-backed work against codebase and persist outcomes to GitHub comments.

2|1|Updated Mar 4, 2026
Search Tags:#workflow#documentation#context#github#adr#prd#grill
One-click install
npx skills add https://github.com/ladislas/mypac --skill pac-grill-with-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pac-grill-with-docs
Source: https://github.com/ladislas/mypac/tree/main/skills/pac-grill-with-docs
Command: npx skills add https://github.com/ladislas/mypac --skill pac-grill-with-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grill issue-backed work against the codebase and project language, then persist durable outcomes to GitHub issue updates, ADR comments, PRD comments, and sparing CONTEXT.md edits.

Core Features & Use Cases

  • Guided grilling flow: Step-by-step questioning to clarify scope from an issue/PR.
  • Persistent decisions: Auto-publishes ADR comments, PRD references, and CONTEXT.md updates.
  • GitHub-first workflow: Primary scratchpad on issues with optional repo-local artifacts.
  • Scope refinement: Rewrites or clarifies the issue scope when needed.

Quick Start

Start by selecting the target issue or PR URL, then begin questioning until a shared plan emerges.

Frequently Asked Questions about pac-grill-with-docs

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

FAQPage Schema
How do I document GitHub issue decisions directly back to the repository?▼

To document GitHub issue decisions, you can grill issue-backed work against the codebase and persist durable outcomes as ADR comments, PRD comments, and CONTEXT.md updates directly on the GitHub issue.

What is the best way to clarify project scope from a GitHub issue before coding?▼

The best way to clarify project scope is using a guided grilling flow that questions issue details against the codebase until a shared plan emerges, rewriting the issue scope when needed.

Do I need GitHub access to generate ADR and PRD documentation for my workflow?▼

Yes, you need reliable GitHub access to generate ADR and PRD documentation, because the workflow requires reading issue details and persisting planning outputs as comments and issue updates.

How do I start grilling an issue against my codebase and project language?▼

You start grilling an issue by selecting the target GitHub issue or PR URL, then answering step-by-step questions until a shared technical plan emerges and durable notes are published.

When should I use durable GitHub-backed notes versus local repository documentation?▼

Use durable GitHub-backed notes when working from a GitHub issue or PR and needing grilling plus persistent planning outputs, using the GitHub issue as your primary scratchpad with optional repo-local artifacts.

What limitations exist when generating ADR comments and PRD references from issues?▼

Limitations include requiring adherence to ADR and PRD templates for repeatable outputs, and the grilling flow depends on reliable GitHub access to persist durable outcomes to issue updates and CONTEXT.md.

Related Skills

Explore More Software Engineering Skills→
lutzcc1lutzcc1

github-issue-analyzer

Analyze GitHub issues to generate structured implementation plans with tasks and milestones.

Community
Advanced
glhewettglhewett

issues-close

Close TOML issues by updating metadata, appending comments, and committing.

Community
Intermediate
Davie521Davie521
7

to-prd

Synthesize a structured PRD from conversation context and project files.

Community
Advanced
zli5460zli5460
2

github-issues

Create, search, label, and assign GitHub issues via API calls and command-line tools.

Community
Intermediate