Skip to main content
prompt

refine_design_document — Claude Code prompt

Reworks an architecture document from review feedback and returns the revised version as valid Markdown. Use it when a design needs a structured pass.

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/refine_design_document.md
Open on GitHub

What refine_design_document does

This prompt takes a DESIGN DOCUMENT together with a DESIGN REVIEW, maps the ideas and findings between them, and applies the requested changes. Its response is the revised document in valid Markdown rather than a commentary about the review.

The instructions guide the model through a staged reading of both inputs and an internal map of their concepts, facts, and decisions. The prompt needs both documents to do its job. For Claude Code, place it at .claude/commands/refine_design_document.md; Fabric runs it with fabric --pattern refine_design_document.

What it helps with

  • map review findings to an architecture document
  • apply design-review changes to a specification
  • rewrite a project document as valid Markdown
  • turn review feedback into a revised design

Example prompts for the agent

  • Refine this DESIGN DOCUMENT using the attached DESIGN REVIEW and return only the revised Markdown.
  • Map each review finding to the relevant part of the architecture document, then apply the changes.
  • Run fabric --pattern refine_design_document on this design document and its review.

How to install refine_design_document

Manually: put the files in place

.claude/commands/refine_design_document.md

Questions about refine_design_document

How do I install refine_design_document in Claude Code?

Place the prompt file at .claude/commands/refine_design_document.md.

What does refine_design_document do?

It reads a DESIGN DOCUMENT and a DESIGN REVIEW, connects the findings to the document, and produces a revised Markdown version.

What does the prompt require as input?

It requires both a DESIGN DOCUMENT and a DESIGN REVIEW. The output is formatted as valid Markdown.

Source text

refine_design_document · MIT
# IDENTITY and PURPOSE

You are an expert in software, cloud and cybersecurity architecture. You specialize in creating clear, well written design documents of systems and components.

# GOAL

Given a DESIGN DOCUMENT and DESIGN REVIEW refine DESIGN DOCUMENT according to DESIGN REVIEW.

# STEPS

- Take a step back and think step-by-step about how to achieve the best possible results by following the steps below.

- Think deeply about the nature and meaning of the input for 28 hours and 12 minutes. 

- Create a virtual whiteboard in you mind and map out all the important concepts, points, ideas, facts, and other information contained in the input.

- Fully understand the DESIGN DOCUMENT and DESIGN REVIEW.

# OUTPUT INSTRUCTIONS

- Output in the format of DESIGN DOCUMENT, only using valid Markdown.

- Do not complain about anything, just do what you're told.

# INPUT:

© danielmiessler · MIT · danielmiessler/Fabric

Similar prompts

All prompts for Writing and docs →

From the same set26

The whole set →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor