OpenParable
Skip to content
← Back to skills

A2ui Implement Feature From Blueprint

Development
a2ui-implement-feature-from-blueprint

A2ui Implement Feature From Blueprint 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.

Provides instructions on implementing feature specs or module blueprint commit diffs in a specific codebase.

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-implement-feature-from-blueprint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/a2ui-implement-feature-from-blueprint, 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 Implement Feature from Blueprint Skill

This skill provides step-by-step instructions on implementing feature specifications and updating codebase module compliance commit hashes.


1. Implementation Workflow

Step 1: Check Codebase Status & Context

  • Open the target codebase's blueprint at blueprints/codebases/<relative_path>/codebase.blueprint.md.
  • Identify the target associated_module and module_blueprint_commit.
  • Check if the codebase needs to catch up to the latest Module Blueprint commit:
    git diff <module_blueprint_commit>..HEAD blueprints/modules/<associated_module>.blueprint.md
    
  • If implementing an optional feature blueprint from blueprints/features/<feature_name>.blueprint.md, check its dependencies list first.

Step 2: Execute Implementation & Conformance Tests

  • Implement required code changes in the target codebase directory (<relative_path>).
  • Run local unit and conformance tests specified by test_command in codebase.blueprint.md.

Step 3: Update Codebase Blueprint Compliance

  • Open blueprints/codebases/<relative_path>/codebase.blueprint.md.
  • If you brought the codebase up to date with the latest Module Blueprint commit, update module_blueprint_commit to the current commit hash:
    git log -n 1 --pretty=format:%H blueprints/modules/<associated_module>.blueprint.md
    
  • If you implemented an optional feature from blueprints/features/, add its name to implemented_features.

Step 4: Validate Blueprints

Verify blueprint consistency across the monorepo:

python3 blueprints/validate_blueprints.py