Product Founder OS

What it is

product-founder-os is a practical repository asset for product development with GPT and/or Codex. Its job is not to produce one-shot output and disappear. Its job is to give product work a durable structure: what you are building, what changed, what comes next, and what is actually done.

AI-assisted product work often breaks in familiar ways. Implementation starts before the product is properly defined. Docs drift away from what is actually being built. Scope changes happen in conversation but never make it into the repository. “Done” gets claimed long before completion is real. This repository exists to reduce that drift by treating files such as project seed, product brief, functional spec, roadmap, current sprint, change requests, and done definition as source-of-truth operating files.

Who it is for

This repository is for people who want to build products with GPT and/or Codex across multiple sessions without losing coherence.

• Solo builders starting from a vague product idea
• People planning a small SaaS or static tool before implementation
• Repositories that already have code but weak product definition
• Projects that need explicit scope handling and change tracking
• Builders who want to know what is truly done and what is still open

It is less suitable if you only want a tiny one-off script immediately, or if you want to skip planning entirely and jump straight into code.

What it does

Turns vague ideas into working product docs

It helps organize project seed, product brief, target user, problem, scope, and non-goals into a usable starting point.

Connects specs to planning

It gives the repository a functional spec, roadmap, task backlog, current sprint, and done definition so implementation has a real baseline.

Makes change visible

change-requests.md makes requirement changes explicit and encourages updating docs before changing implementation direction.

Checks the foundation

Helper scripts can check baseline doc presence, markdown link integrity, placeholder leakage, and malformed code fences.

Modes

Discover

Figure out what should be built and turn that into a usable starting point.

Define

Clarify the product, the user, the problem, the scope, and the intended behavior.

Plan

Turn the current definition into milestones, backlog items, and an executable current sprint.

Build

Move implementation forward against the current sprint while keeping the docs aligned with reality.

Adjust

Handle requirement changes explicitly instead of letting them silently alter the project direction.

Ship

Review whether the current increment is actually complete and whether the handoff or release state is honest.

What’s included

Core instructions

README.md, SKILL.md, AGENTS.md, DISCLAIMER.md, and LICENSE.

Documentation

docs/ covers intake, definition, spec, design, planning, execution, quality, and handoff.

Examples and templates

examples/ contains one worked static-tool example plus lighter SaaS and content-site examples. templates/ provides reusable starting points.

Scripts

create_project_docs.py, check_doc_links.py, validate_foundation.py, and bootstrap_new_product.py.

How to use it

This repository makes the most sense when you treat it as an operating repo, not just a folder of documents.

1. Read README.md to understand the repository’s role and workflow.
2. Read SKILL.md to see how the assistant is expected to behave.
3. Read AGENTS.md and the current core docs to understand the current product state.
4. If the product is still undefined, ask what should be built before starting major implementation.
5. Update the baseline docs first: project seed, brief, functional spec, roadmap, backlog, current sprint, and done definition.
6. Proceed with implementation against current-sprint.md.
7. If requirements change, update change-requests.md and the source-of-truth docs before changing direction.

If you only want the fastest introduction, start with the README and the worked static-tool example. If you want to use it seriously, go through the validation scripts and bootstrap helper as well.

Bootstrap helper

If you want starter docs for a new product idea, the repository includes a helper script:

python3 scripts/bootstrap_new_product.py "Your Product Name" --one-line "One-line description" --user "target user"

This generates starter files for a seed, brief, functional spec, roadmap, current sprint, and done definition. It is not a finished-product generator. It gives you a usable starting point that still needs real clarification, prioritization, and human review.

Why NicheWorks publishes it

NicheWorks publishes small, practical tools and workflow assets meant to be useful in real work. product-founder-os fits that line as a repository asset for a common operational problem: AI-assisted product work that drifts because the product was never clearly defined or kept current.

It is not presented as a magic product generator. It is presented as a useful, durable foundation for keeping product work from collapsing into vague sessions, stale docs, and fake completion.

FAQ

Links

Disclaimer

This page and the linked repository are published for informational and practical workflow purposes. Completeness, suitability for a specific purpose, and product success are not guaranteed. Final product decisions and implementation decisions still require human review.