define-blueprint

Generate schema-valid YAML blueprints standardizing chapters, compliance rules, and export formatting.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill define-blueprint-ameng2001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: define-blueprint
Source: https://github.com/Ameng2001/astra-studio-plugins/tree/main/studio-docs/skills/define-blueprint
Command: npx skills add https://github.com/Ameng2001/astra-studio-plugins --skill define-blueprint-ameng2001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid inconsistent document structures and missing compliance requirements by creating a reusable blueprint that standardizes chapters, writing rules, and export formatting for any project document type.

Core Features & Use Cases

  • Blueprint discovery & override: Uses a project-level blueprint first, with built-in templates as a fallback so you can customize for your organization.
  • Blueprint authoring: Produces a YAML blueprint covering chapter structure, compliance rules, and writer guidance for a specific document type and lifecycle stage.
  • Validation-ready output: Ensures the resulting blueprint follows the expected schema (chapter ids, lifecycle stage, and compliance structure) so it can be used immediately by downstream document planning and generation.
  • Use Case: When you need to create a tailored feasibility study document for a government IT project, you can either start from the built-in blueprint or create a new variant with your required policies, standards, and chapter mapping.

Quick Start

Run define-blueprint to generate a new YAML blueprint for your document type and save it to studio/blueprints/ so it can be used by subsequent planning and document generation steps.

Frequently Asked Questions about define-blueprint

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

FAQPage Schema
How do I create a YAML document blueprint that standardizes chapter structure and compliance rules?

A document blueprint is a YAML configuration that standardizes chapter structure, compliance rules, and export formatting for a specific project document type and lifecycle stage, ensuring consistent document generation.

How do I customize a built-in template for a specific project lifecycle stage?

Customize a built-in template by creating a project-level blueprint override. The system uses project-level blueprints first, falling back to built-in templates, allowing you to tailor chapter mapping and compliance for stages like initiation, design, or delivery.

Can I generate a schema-valid YAML blueprint for government project compliance?

Yes, you can generate a schema-valid YAML blueprint for government projects. It produces validation-ready output with correct chapter ids, lifecycle stages, and compliance structures, ensuring the customized blueprint passes downstream schema checks.

What is the best way to standardize export formatting across different project documents?

The best way to standardize export formatting is to define it within a document blueprint. By specifying export settings alongside chapter structures and compliance rules in YAML, you ensure consistent output across all documents of that type.

Does the document blueprint support compliance rules for feasibility studies and procurement responses?

Yes, the document blueprint supports compliance rules for feasibility studies and procurement responses. It applies to authoring or tailoring templates for lifecycle stages including justification, procurement, and response, embedding required policies and standards.