---
name: a2ui-blueprint-maintenance
description: Manage the evolution, merging, archiving, and cleanup of specifications and blueprints across the workspace.
metadata:
  internal: true
title: a2ui-blueprint-maintenance
canonical_url: https://skilld.dev/gh/a2ui-project/a2ui/a2ui-blueprint-maintenance
last_updated: 2026-11-12T06:16:11.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install a2ui-project/a2ui/a2ui-blueprint-maintenance`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/a2ui-blueprint-maintenance`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/a2ui-project/a2ui/a2ui-blueprint-maintenance) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/a2ui-blueprint-maintenance`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/a2ui-blueprint-maintenance --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/a2ui-blueprint-maintenance --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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/`:
     ```bash
     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:
     ```bash
     python3 blueprints/validate_blueprints.py
     ```

### **Recipe B: Updating a Feature Blueprint**

When updating an active feature blueprint in `blueprints/features/<feature_name>.blueprint.md`:

1. Update the feature blueprint specification.
2. When updating a codebase to conform to the revised feature blueprint, update that feature's pinned commit hash under `implemented_features` in `blueprints/codebases/<relative_path>/codebase.blueprint.md`:
   ```bash
   git log -n 1 --pretty=format:%H -- blueprints/features/<feature_name>.blueprint.md
   ```
3. Run the blueprint validator:
   ```bash
   python3 blueprints/validate_blueprints.py
   ```

### **Recipe C: 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:
   ```bash
   python3 blueprints/validate_blueprints.py
   ```
