A Second Opinion It Didn't Write
An agent reviewing its own plan shares its own blind spots. Wire a different vendor's model in as a deterministic gate, and a fail verdict re-engages planning before a line of code exists.
#workflow
13 posts tagged #workflow.
A Skill That Writes Your Skills
Your debugging ability isn't intelligence, it's a procedure — and procedures are exactly what you can write down once and hand to an agent. Bootstrap the whole library with a meta-skill.
Build the Glossary the Agent Wrote
Vague prompting isn't a skill gap you fix by writing longer prompts. It's a missing shared vocabulary — and the fix is a committed glossary, not a personal habit.
Cache the Explore
The codebase is the strongest steering signal you have — stronger than your prompt or your rules. So pay the exploration cost once, freeze it into a file, and feed it to every run.
Commission the Skill, Don't Write It
You don't author a skill from a blank page. You send a subagent to research the problem once, and the research becomes the skill — a build artifact, not a document.
Design the Codebase Your Agent Can Read
The highest-leverage thing you can do for your agent isn't a better prompt — it's a better interface. Deep modules are persistent context the agent reads at a glance.
Destination and Journey
Hand the agent two committed documents — a requirements doc that fixes the destination and a phased plan that fixes the journey — and a feature too big for one window ships correctly anyway.
Full Autonomy Is Just a Small Blast Radius
The blocker to running an agent overnight is never capability. It's trust. And you don't earn trust with a smarter model — you earn it with a smaller blast radius.
Inject the Reminder When the Agent Forgets
Your rules file is necessary but not sufficient. Persistent context degrades as the window fills — so move the rule that keeps getting ignored into a hook that fires at the exact moment it matters.
Package the Workflow, Not the Prompt
A plugin isn't a convenience wrapper. It's how a workflow survives leaving your laptop — the difference between a personal habit and a team standard.
The Loop That Re-Reads Its Diary
An autonomous agent isn't a bigger context window. It's a tiny window run many times, where the git log — not the chat history — carries the decisions between passes.
The Relay, Not the Window
A million-token window won't fix a long build. Externalize state to a plan file and run a relay across fresh sessions, because quality dies long before the window fills.
Your Backlog Is the Prompt
Hand-passing one plan per run keeps you inside the loop doing task selection for the agent. Pipe your whole issue tracker in and let it pick the next ticket itself.