blueprint

Convert design and research markdown artifacts into implementation blueprints and prompts.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill blueprint-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blueprint
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/blueprint
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill blueprint-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts high-level design and research artifacts into a concrete, implementation-ready blueprint and a companion implementation prompt, reducing ambiguous handoffs between design and engineering.

Core Features & Use Cases

  • Prerequisite validation: Verifies presence of docs/design/*.md and reads findings trackers, with an option to force-run.
  • Structured outputs: Produces a templated blueprint and an implementation prompt saved to docs/blueprints/ and docs/prompts/ using strict filename and section conventions.
  • Governance and pipeline guidance: Enforces required sections, stop conditions, and next-step pipeline rules so teams enter /plan with a consistent, high-quality artifact.
  • Use Case: Turn a completed design doc for "real-time WebSocket notifications" into a step-by-step implementation blueprint and a /plan prompt that engineering can execute.

Quick Start

Run the command /blueprint add real-time WebSocket notifications to the monitoring dashboard to generate a blueprint and an implementation prompt from existing design and research documents.

Frequently Asked Questions about blueprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert design docs into implementation-ready blueprints?

To convert design docs into implementation-ready blueprints, this skill transforms markdown files in docs/design/ and docs/research/ into a detailed blueprint and implementation prompt. It enforces strict filename and section templates to reduce ambiguous handoffs.

What is the best way to generate implementation prompts from research markdown artifacts?

Generating implementation prompts from research markdown artifacts is done by reading findings trackers and applying governance rules to produce a companion prompt. Outputs are saved to docs/prompts/ using strict section conventions to prepare files for the plan stage.

Do I need existing design markdown files to create an implementation blueprint?

Yes, you need design markdown files to create an implementation blueprint. The skill validates for the presence of docs/design/*.md or docs/research/*.md, but you can bypass this prerequisite validation by running with an explicit --force flag.

Can I enforce strict section templates when transforming design docs into engineering specs?

Enforcing strict section templates when transforming design docs into engineering specs is a core feature. The skill applies required sections, stop conditions, and pipeline guidance so engineering teams enter the plan stage with a consistent, high-quality artifact.

What happens if my design research artifacts are missing required sections for blueprint generation?

If design research artifacts are missing required sections, blueprint generation enforces stop conditions and pipeline rules to prevent incomplete specs. You must ensure your markdown files meet the strict template conventions before generating the implementation prompt.