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

How to run a rigorous coding task through the p3 mode router with P3 Stack

Install the skills, map models once, then let p3-mode pick a playbook for a request.

Who it is forA developer using T3 Code who wants agent work on a repo to follow a strict engineering process instead of ad hoc prompting.

The problemAgent-written code often skips investigation and verification, which leads to slop that is hard to review.

The outcomeA working install, a models file in p3-models.md, and a task completed through a playbook chosen by p3-mode.

What you need first

  • T3 Code installed, since install.sh links skills for it to read
  • git and a shell to run install.sh
  • At least one model provider available through T3 Code's orchestrator_capabilities
  • A git repository to work on

Steps

  1. Run git clone https://github.com/uzairansaruzi/p3-stack.git to fetch the repo.
  2. Run cd p3-stack and then ./install.sh to link the skills into ~/.agents/skills/.
  3. In T3 Code, run /setup-p3 so it maps each role to a provider and model you have, writing p3-models.md.
  4. Run /p3-mode and describe your task; p3-mode picks a playbook and calls the other skills as needed.
  5. Check the result against the verification the playbook ran before accepting the change.

Prompt for your agent

In the repo at <repo-path>, use the p3-stack skills: run /setup-p3, then run /p3-mode on the task <task description>. Expected output: the code change plus the playbook steps taken. Verify that p3-models.md exists and lists a provider and model for each role.

Caveat. The README lists the install and setup commands but does not show a sample run, so expect to read the playbook output to learn how it behaves on your repo.

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