TESTINPROD.CO
CONDUCTOR FRAMEWORK v0.1 // UPDATED 2025-12-22

CONDUCTOR FRAMEWORK

A lightweight product development system designed for solo developers and small teams working with LLMs. It lives in your codebase as folders + markdown — not another SaaS tool.

DOWNLOAD THE SYSTEM

// OPEN SOURCE

GET THE CODE
The Conductor Framework is open source. Enter your email to unlock the GitHub repository and get notified about workflow updates and new templates.
>

HOW IT WORKS

// HUMAN-FRIENDLY GUIDE

// IN PLAIN ENGLISH

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.

GOAL
Ship more, with less chaos
UNIT
Problems → PRDs → Implementations
MODE
Human leads, AI assists
>> WHEN TO USE IT
GOOD FIT
  • >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.
NOT THE POINT
  • >Perfect planning or heavy process.
  • >Replacing Jira for a 50-person org.
  • >Docs for docs’ sake.
  • >Big-bang roadmaps with no shipping loop.
>> WORKFLOW
Roadmap (what could we build?)
    ↓
Backlog (what should we build next? broken into user stories)
    ↓
PRD (what exactly are we building? for whom? why?)
    ↓
Implementation (how do we build it?)
    ↓
Workbench (building it now)
    ↓
Archive (done)

Two roadmap lenses: Themes (evergreen epics by product area) and Objectives (time-bound initiatives with KRs + phases).

FOLDER
PURPOSE
0-Key Metrics
The numbers that matter. North star and category metrics.
1-Workbench
Active desk: Inbox, scratchpad, current implementation work.
2-Backlog
User stories broken down from epics, prioritized and ready to build.
3-PRDs
Product requirements docs. The what, who, and why.
4-Implementations
Technical plans. The how.
5-Roadmaps
Themes (evergreen epics) + Objectives (time-bound OKRs).
6-Reference Docs
Stable identity docs: vision, architecture, personas, etc.
7-AI Protocols
Initialization prompts for LLMs and agents.
8-Templates
Templates for all document types.
9-Archive
Completed work.
>> HOW YOU ACTUALLY USE IT
LOOP A — CAPTURE

Dump everything into Workbench/Inbox. Ideas, bugs, random thoughts, links. No sorting. No guilt.

LOOP B — SHAPE

Turn the best items into a problem statement (Theme epic), then break it into a few user stories in the Backlog.

LOOP C — DECIDE

Write a short PRD that makes scope explicit (in/out) and defines success criteria. If you can’t define “done,” you can’t ship.

LOOP D — SHIP

Create an Implementation Plan with phases + tests. Move it into Active Work. Ship. Archive when complete.