Idea → specification

Turn a rough idea into a spec a team can challenge.

Frame the product, expose consequential unknowns, map the user flow, resolve decisions, and define acceptance before implementation begins.

Single-user license · 7-day refund window · 12 months of maintenance updates

BuildBrief OS cover

01 / Outcome

A reviewable artifact, not a confident paragraph.

A bounded software specification with traceable decisions, explicit non-goals, an implementation sequence, and observable acceptance tests.

When the evidence is incomplete, the workflow narrows the conclusion, marks the gap, and returns the next verification instead of inventing project facts.

02 / Workflow

7 focused skills, each with one job.

  1. 01

    Frame the idea

    A one-page product frame without false certainty

  2. 02

    Research context

    Facts, evidence, inference, and unknowns kept separate

  3. 03

    Map the flow

    User and system behavior aligned step by step

  4. 04

    Resolve decisions

    Material ambiguity turned into reviewable choices

  5. 05

    Write the spec

    One bounded implementation reference

  6. 06

    Plan implementation

    Buildable vertical slices tied to the spec

  7. 07

    Define acceptance

    Observable behavior for review and testing

03 / Fictional demonstration

Worked example: appointment reminders

A fictional clinic request starts with an unchosen email provider and unknown retry rules. The workflow does not fill those gaps with guesses; it separates what can be specified now from what blocks integration and release approval.

This excerpt is a fictional demonstration. It is not a customer result, production test, approval, or performance claim.

Known boundary

One email, 24 hours before a confirmed appointment

Explicit gaps

Provider, consent evidence, retry ceiling, approved copy

Reviewable artifact

Requirements, non-goals, acceptance scenarios, next verification

04 / Included

Everything needed to install, adapt, and inspect the workflow.

  • 7 native SKILL.md workflows
  • 7 portable prompts
  • 7 reusable Markdown templates
  • 3 realistic worked examples
  • Quick-start PDF, compatibility guide, license, and 12 months of maintenance updates

For

Use it when the work needs a boundary.

Developers, product-minded freelancers, and solo founders who need a decision-complete brief before they build.

Not for

Keep the limits visible.

Buyers looking for automated market validation, stakeholder approval, vendor access, or guarantees that a product will succeed.

05 / Questions

Compatibility, evidence, and execution.

Is this a generic prompt collection?

No. Each workflow has a narrow trigger, required inputs, a procedure, an output contract, and rules for handling missing evidence.

Which assistants are supported?

The native filesystem skills are designed for Codex and Claude custom Agent Skills. Portable copy-and-paste prompts are included for other assistants. Availability depends on the model, plan, tools, and permissions you use.

Does the pack run code or change systems automatically?

No bundled workflow contains scripts or hidden network calls. A workflow may guide an assistant that already has tools, but consequential actions still require the user's authorization.

Are outcomes guaranteed?

No. Results depend on the context supplied, available evidence, model capability, tool access, and human review.

Replace improvised prompting with a reviewable workflow.

Native skills, portable prompts, templates, worked examples, and a practical quick start.

Get BuildBrief OS — $29