Capability · Control layer

Twelve versioned plan documents per product. Agents author, you approve.

A product is a strategic container, not a doc. PACKWOLF gives every product twelve structured plan documents, strategy, market research, GTM, marketing plan, sales plan, technical architecture, decisions log, more. Agents fill them in via tool calls. Every section is versioned.

12
Document types per product
Versioned
Every section
Revertable
Any prior
Agent-writable
Via tools
packwolf.app · Product OS
Live screenshot
Product OS screenshot
The product hub. All twelve plan documents per product, version history per section, agent-writable.
What it actually does

The parts that make this work.

Twelve structured documents.

Strategy & Positioning. Market Research. Business Plan. Features & Capabilities. GTM. Marketing Plan. Sales Plan. Release Notes. Technical Architecture. UI/UX Plan. Decisions Log. Metrics & Success Criteria.

Every section is structured.

Sections have field types, text, list, table, structured object, persona cards, ADR-style entries, 4-quadrant SWOT grids. Editing is field-aware, not free-form prose.

Section guidance, always.

Each section ships with instructional text explaining what belongs there and how to think about it. The Product page is a structured thinking framework.

Version-controlled by section.

Edit a section, get a new version snapshot of that document. Revert any section to any prior version. Diffs show what changed.

Agent-writable by design.

Specialist agents (marketing, sales, technical, research) write directly into product sections via tool calls. Operators chat with the Head of Product agent; specialists do the writing.

Linked to projects, goals, tasks.

Products own goals; goals own projects; projects own tasks. The whole strategy-to-execution stack hangs off the product page.

How it works

The path through product os.

  1. 01

    Create a product.

    Set the basics, name, owner, audience. Twelve plan documents instantiate with section scaffolding and guidance text. Sections start empty.

  2. 02

    Assign specialist agents.

    Marketing agent writes the Marketing Plan. Tech architect writes the Tech Architecture doc. Research agent writes Market Research. Each agent has scoped section access.

  3. 03

    Agents fill sections via tools.

    pw_product_read pulls a section's current content. pw_plan_edit writes a new version. pw_spec_edit edits structured spec sections. The whole loop respects approvals.

  4. 04

    Versions snapshot per edit.

    Each edit creates a new version of that document with a diff vs. the prior. Revert restores any version. Two operators can compare different versions side by side.

  5. 05

    Approvals gate build-readiness.

    Sections that downstream work depends on (specs, technical architecture) require approval. Until approved, downstream tasks see the doc as not-yet-build-ready.

  6. 06

    Goals, projects, tasks cascade.

    Products own goals via foreign key. Goals own projects. Projects own tasks. The kanban, the calendar, and the issues board all read from this hierarchy.

Common questions

Things engineers actually ask.

Structured plan types match how strategy actually works. Marketing thinks differently than tech architecture; both are different from a decisions log. Splitting into typed documents makes each one tractable, and gives you per-document version history and approval policies.

Related capabilities
CapabilityTask managementCapabilityApprovalsCapabilityWorkflows
Source: docs/PRODUCT.md

See it in your workspace.

Closed-beta cohorts are small. Tell us what you'd want this capability to handle for your team.

Request beta access