Tutorial: Build a Feature Brief to Engineering Plan Workflow in PromptPlan

Goal

Build a reusable workflow that turns a product feature brief into:

• clarified scope
• technical breakdown
• implementation tasks
• edge-case review
• exported engineering plan

Step 1: Create the workflow

Open /workflows/new and set:

• title: Feature Brief to Engineering Plan
• summary: Turn a feature brief into an implementation-ready engineering plan.
• category: engineering
• visibility: private

Step 2: Add workflow inputs

Create these inputs:

• feature_description as long_text
• constraints as long_text
• target_platform as select

Suggested select options for target_platform:

• web
• mobile
• api
• full_stack

Step 3: Add the clarify step

Create a reason step called clarify_goal.

Prompt shape:

Clarify the product goal, user impact, in-scope work, out-of-scope work, and key assumptions.

Target platform: {{workflow.input.target_platform}}
Constraints:
{{workflow.input.constraints}}

Feature brief:
{{workflow.input.feature_description}}

Step 4: Add the technical breakdown step

Create a second reason step called technical_breakdown.

Use the previous output:

Create a technical breakdown from the clarified goal below.

{{step.previous.output}}

Ask for:

• affected systems
• API or data implications
• frontend implications
• rollout risks

Step 5: Add the implementation tasks step

Create a generate step called implementation_tasks.

Reference the technical breakdown directly:

Turn this technical breakdown into milestones and engineering tasks:

{{step.technical_breakdown.output}}

Step 6: Add the review step

Create a review step called review_edge_cases.

Have it critique:

• missing edge cases
• failure modes
• privacy or security concerns
• performance concerns

Step 7: Add the export step

Create an export step called export_plan.

Combine the outputs into one final markdown artifact:

• goal and scope
• technical breakdown
• implementation tasks
• risks and edge cases
• rollout notes

Step 8: Run the workflow

Use a real feature brief, then:

1. choose balanced
2. click Run all
3. inspect the technical breakdown step
4. inspect the review step
5. export the final output

Step 9: Improve it

After the first run, refine one part at a time:

• add sharper constraints
• split a weak step into two smaller steps
• pin a stronger model only on the reasoning step that needs it
• improve the export format so it matches how your team actually works