DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to align an agent on a change before any code is written with Skills

Run a grilling session so the agent asks detailed questions before it edits your repo.

Who it is forA developer about to ask a coding agent for a feature who has seen past builds miss what they meant.

The problemMisalignment is the most common failure mode: the agent builds something that does not match what you wanted.

The outcomeA clarified plan, plus shared terms and decisions recorded in the project's domain docs before implementation starts.

What you need first

  • A coding agent that supports the plugin or skills install route, such as Claude Code or Codex
  • A project repository the agent can read and edit
  • Optional: an issue tracker such as GitHub or GitLab, or a local folder for tickets

Steps

  1. Install the plugin in Claude Code with claude plugin install mattpocock-skills@claude-plugins-official.
  2. In your repo, run /setup-matt-pocock-skills once and answer the questions about issue tracker, triage labels, and where docs go.
  3. Run /grill-with-docs and describe the change you want.
  4. Answer the agent's questions until the plan is clear, and let it update the glossary and ADRs as you go.

Prompt for your agent

In the mattpocock/skills repo's grill-with-docs workflow, interview me about the change described here: <feature description>. Expected output: a short list of resolved decisions and updated GLOSSARY.md entries or ADRs. Verify that every new term in the output appears in the glossary file.

Caveat. The grilling session only helps if you engage with the questions, and the Skills expect the setup step to run once per repo before the engineering Skills are used.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page