Project Spec Workflow: Turn Scattered Notes into a PRD

Inputs (copy/paste)

Start with a note like PRD - <Project>.md and paste or link:

• Problem statements from meetings
• Constraints (time, budget, tech)
• Success metrics
• Existing decisions and tradeoffs

The hub note is the input. The PRD is the output.

Outline prompt

Prompt idea:

• "Create a PRD outline for this project. Keep it to 8 to 12 headings. Ask me 3 clarifying questions at the end."

Answer the questions inside the note so SystemSculpt can incorporate them.

Fill the PRD with vault context

Prompt idea:

• "Fill the PRD sections using only the information in the hub note and linked notes. Where there is missing info, add a TODO question instead of guessing."

Turn the PRD into tasks

Prompt idea:

• "Extract milestones and tasks. For each task, include a one-sentence definition of done. Keep tasks atomic."

If you use semantic search, you can also surface related work automatically: Embeddings & Search.

Failure modes + fixes

• Failure mode: PRD sections are complete, but assumptions stay implicit. Fix: Add an explicit Assumptions section and force review before task extraction.
• Failure mode: Tasks are too large to execute or estimate. Fix: Require each task to fit one owner and one clear definition of done.
• Failure mode: Missing context gets guessed instead of flagged. Fix: Keep "add TODO question instead of guessing" in every generation pass.

Definition of done

I mark this workflow complete when:

• The PRD has explicit goals, non-goals, risks, and open questions.
• Every milestone has tasks with a definition of done.
• Unknowns are tracked as TODO questions, not guessed assumptions.

Next step based on your intent

• If you want this shipped as a production workflow with governance, apply here: AgentOps application.
• If you want to run it yourself in your vault, use SystemSculpt Pro pricing.

Related template

Start from a consistent PRD format with the Obsidian Project Spec Template.