OpenParable
Skip to content
← Back to skills

A2ui Blueprint Maintenance

Development
a2ui-blueprint-maintenance

A2ui Blueprint Maintenance is an Agent Skill for development published in the a2ui-project/a2ui repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Manage the evolution, merging, archiving, and cleanup of specifications and blueprints across the workspace.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/a2ui-project/a2ui/blob/HEAD/blueprints/skills/a2ui-blueprint-maintenance/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/a2ui-blueprint-maintenance, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

A2UI Blueprint Maintenance Skill

This skill provides administrative recipes for merging feature specifications into Module Blueprints and archiving feature blueprints.


1. Lifecycle & Archiving Recipes

Recipe A: Merging & Archiving a Feature Blueprint (Promoting to Required)

When a feature specification in blueprints/features/<feature_name>.blueprint.md is ready to be merged into its target Module Blueprint(s):

  1. Merge Specification into Module Blueprint:
    • Open each target Module Blueprint listed under module_blueprints (e.g. blueprints/modules/a2ui_core.blueprint.md).
    • Integrate the feature's architectural rules, schemas, and behaviors into the module blueprint.
    • Do NOT add anything to an included_features list (module blueprints do not list included features).
  2. Archive the Feature Blueprint:
    • Move the feature blueprint file into blueprints/features/archived/:
      git mv blueprints/features/<feature_name>.blueprint.md blueprints/features/archived/
      
    • Once in blueprints/features/archived/, the feature is permanently archived and its requirements are part of the module blueprint.
  3. Commit & Validate:
    • Run the blueprint validator:
      python3 blueprints/validate_blueprints.py
      

Recipe B: Archiving Deprecated Optional Features

If an optional feature in blueprints/features/<feature_name>.blueprint.md is deprecated or abandoned without being merged:

  1. Move it to blueprints/features/archived/<feature_name>.blueprint.md.
  2. Run validation to ensure repository consistency:
    python3 blueprints/validate_blueprints.py