Shelfery Product Directory

This directory is where formal product specifications for Shelfery will live: a product brief, product requirements, a feature inventory, acceptance criteria, and a product-level roadmap. None of those exist yet in substantive form.

Why this directory currently contains placeholders

Formal product specification work has not started. Writing real requirements, features, or acceptance criteria before the venture brief and brand direction are sufficiently confirmed would mean inventing product scope rather than deriving it from validated direction — something this venture's documentation is explicitly required to avoid (see ventures/shelfery/AGENTS.md, section 6, and ventures/shelfery/docs/strategy/venture-brief.md).

Each file in this directory currently explains what it will eventually contain, why it's empty now, and what needs to happen before it can be filled in — rather than being a one-line stub.

What needs to happen before this directory becomes real

1. The strategy direction in ventures/shelfery/docs/strategy/ — particularly venture-brief.md, target-users-and-jobs.md, and brand-and-positioning.md — needs to move from working hypotheses toward validated, reasonably confident direction.
2. A product-brief.md can then be written, describing the intended product at a level suitable for scoping requirements.
3. product-requirements.md and feature-inventory.md follow from an approved product brief.
4. acceptance-criteria.md follows per-feature, once features exist in the feature inventory.
5. Once product requirements exist, real architecture work can begin — see ventures/shelfery/docs/architecture/system-context.md.

Files in this directory

• product-brief.md
• product-requirements.md
• feature-inventory.md
• acceptance-criteria.md
• roadmap.md (points to the canonical roadmap statement in docs/strategy/roadmap.md)
• decisions/ — product-level decision records, narrower in scope than venture-level ADRs, to be used once product work begins.

---

Report an issue about this page