A Second Opinion It Didn't Write
An agent reviewing its own plan shares its blind spots. Wire a different vendor's model in as a gate, and a fail verdict re-engages planning before any code.
#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 write down once and hand to an agent. Start with a meta-skill.
Build the Glossary the Agent Wrote
Vague prompting isn't a skill gap you fix with 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 your strongest steering signal - stronger than your prompt or your rules. Pay the exploration cost once, freeze it, 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.
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 context the agent reads at a glance.
Destination and Journey
Hand the agent two committed documents - a requirements doc that fixes the destination, a phased plan that fixes the journey - and a big feature still ships.
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, but 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 - move the ignored rule into a hook that fires when 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 chat history - carries 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 relay across fresh sessions - 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. Pipe your whole issue tracker in and let the agent pick the next ticket itself.