The Simple AI Agent OSFor |
Skills that write PRDs. Workflows that run standups. Agentic flows that ship features end-to-end. Say "red team this" and watch it tear your plan apart.
Start shipping.
HOW IT WORKS
// HUMAN-FRIENDLY GUIDE
The Conductor Framework is a simple way to keep product context, planning, and execution in one place—right next to your code. You don’t “adopt a tool.” You adopt a workflow: capture ideas, shape them into problems, decide what matters, and ship in small loops.
Think of it like a lightweight replacement for a whole stack of tools (docs + tickets + PM rituals), optimized for a team of one using AI. It gives you a consistent place to put things so you can move faster without losing the plot.
- >You’re building in public and need a clear roadmap.
- >You want a repeatable way to go from idea → shipped feature.
- >You use AI daily and want a consistent handoff protocol.
- >You prefer files-in-repo over another SaaS tab.
- >Perfect planning or heavy process.
- >Replacing Jira for a 50-person org.
- >Docs for docs’ sake.
- >Big-bang roadmaps with no shipping loop.
We don't update status fields. We move folders.
Move a folder from Planning to Workbench to start building. Move it to Archive when you ship.
Dump everything into Workbench/Inbox. Ideas, bugs, random thoughts, links. No sorting. No guilt.
Turn the best items into a problem statement (Theme epic), then break it into a few user stories in the Backlog.
Write a short PRD that makes scope explicit (in/out) and defines success criteria. If you can’t define “done,” you can’t ship.
Create an Implementation Plan with phases + tests. Move it into Active Work. Ship. Archive when complete.
THE AI BRAIN
// SKILLS — PRE-BUILT PROTOCOLS FOR YOUR AI
Skills are specialized protocols that turn generic AI into a focused partner. Each skill has a trigger phrase, a clear objective, and a structured output format.
Breaks vague ideas into crisp, testable User Stories with comprehensive Acceptance Criteria. Stays functional — no code planning, just what the user experiences.
Co-creates product requirements through conversation. Challenges assumptions, defines scope boundaries, and ensures the 'Why' is locked in before building.
Transforms chaotic thought streams into structured strategic Epics. Filters noise, checks alignment with your North Star, and places ideas in the right Product Area.
Creates phased battle plans with verification checkpoints. Reviews architecture, discusses trade-offs, and ensures every phase ends with a testable outcome.
Reverse-engineers existing code into documentation. Perfect for legacy codebases or filling out empty Product Areas with accurate technical context.
Cleans file clutter, archives old scratchpads, and optimizes templates. Runs monthly or when things feel messy.
WORKFLOWS
// END-TO-END PLAYBOOKS FOR COMMON SCENARIOS
Workflows are complete operational protocols. Say the trigger phrase, and your AI partner executes a structured sequence.
AI reads your Compass, Workbench, and Active Implementation. You get context without digging through files.
Before moving a folder from Planning to Backlog, get brutal feedback on edge cases, scope creep, and technical risks.
The complete implementation workflow. Create folder, write PRD, plan execution, build, ship, archive.
Finalize a project, capture knowledge, and close the loop properly so nothing gets lost.
Clear your Inbox systematically. Big ideas become Epics, small tasks go to Backlog, everything else to Scratchpad.
Turn a vague idea in Product-Areas into a fully planned folder with PRD and Implementation Plan.
AI interviews you about what worked and what didn't. Updates Decision Log so you don't repeat mistakes.
START SIMPLE
// PROGRESSIVE DISCLOSURE — GROW INTO POWER
You don't need the full system on day one. Start with what you need, add complexity as you grow.
- →0-Compass
- →1-Workbench
- →2-Backlog (Task-Backlog only)
- →8-Archive
- +Inbox capture
- +Task tracking
- +Ship logging
“Context First. Plan Second. Build Third.”
You are not just a coder. You are the orchestrator. You define the “What” (PRD) and the “How” (Plan) so your AI partner can execute with precision.