WorkflowFor DevelopersCode Writing & Debugging

Full Feature Build Workflow.

When building a non-trivial feature from scratch and wanting to think through architecture before writing code.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1950 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
full-feature-build-workflow-4.md Β· 1950 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Code Writing & Debugging
- Use case: Full Feature Build Workflow
- Source task:
  - I need to build the following feature: {{describe_feature}}. Stack: {{stack_components}}. Complete in 3 steps:
  - Step 1: Architecture: data model, API contract (endpoints, request/response shapes), component tree (if frontend), and key design decisions.
  - Step 2: Implementation: write the core code for the backend logic, database query, and primary UI component.
  - Step 3: Testing: write unit tests for the 3 most critical functions and an integration test for the happy path.

# Goal
A 3-part deliverable: architecture design, implementation code, and test suite β€” ready for review.

# Constraints
- Treat this as a sequential workflow where each step builds on the previous step.
- Keep every step clearly labeled and easy to run separately if needed.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
A 3-part deliverable: architecture design, implementation code, and test suite β€” ready for review.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Rolesenior full-stack developer
{{use_case}}Your specific valuefull feature build workflow
{{describe_feature}}Describe featureuser profile settings page
{{stack_components}}Stack componentsReact frontend, Node backend, PostgreSQL database

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When building a non-trivial feature from scratch and wanting to think through architecture before writing code.

PRO TIP

Run Step 1 alone first. Share it with a colleague before proceeding β€” architecture mistakes are 10x cheaper to fix before coding starts.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’