Back to Signal Feed
CodeTracked since May 20, 2026

AIDLC adopts a unified extension selection flow with a community extension contract

This change replaces per-extension opt-in prompts in Requirements Analysis with a single consolidated selection menu and introduces a repository-level community extension index schema to let official and community extensions share one discovery and enablement path.

AIDLC-workflowsRequirements Analysisextensionscommunity-extensions-index.yaml

What Happened

  • This change replaces per-extension opt-in prompts in Requirements Analysis with a single consolidated selection menu and introduces a repository-level community extension index schema to let official and community extensions share one discovery and enablement path.
  • This change replaces per-extension opt-in prompts in Requirements Analysis with a single consolidated selection menu and introduces a repository-level community extension index schema to let official and community extensions share one discovery and enablement path.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Implemented a scalable extension onboarding flow by removing per-extension opt-in prompts and adding a shared extension contract (including integrity and maturity metadata), enabling one menu-driven selection path for existing and future community extensions.

Why Track This

Why It Matters

Workflow operators and extension integrators can now manage extensions from a single selection step, which reduces configuration overhead and lowers the chance of enabling the wrong extension set as the extension catalog grows. This is enabled by unifying official and community extension loading under the same manifest-based `*.opt-in.md` flow, so new community integrations can be added without custom prompt logic or separate onboarding code paths. Watch for index schema or manifest parsing issues and any scripts that still assume the old per-extension prompt behavior, since those could break extension enablement or skip validation.

Impact

Workflow operators and extension integrators can now manage extensions from a single selection step, which reduces configuration overhead and lowers the chance of enabling the wrong extension set as the extension catalog grows. This is enabled by unifying official and community extension loading under the same manifest-based `*.opt-in.md` flow, so new community integrations can be added without custom prompt logic or separate onboarding code paths. Watch for index schema or manifest parsing issues and any scripts that still assume the old per-extension prompt behavior, since those could break extension enablement or skip validation.

What To Watch Next

  • Watch whether AIDLC-workflows becomes a repeated pattern.
  • Track follow-up changes around AI Workflow Automation.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: index_schema_validation_errors, backward_incompatibility_with_old_prompt_workflows.
Open Topic TimelineOpen Technical EventOpen Original Sourceindex_schema_validation_errors / backward_incompatibility_with_old_prompt_workflows / menu_selection_none_or_partial_cases / manifest_hash_or_maturity_misconfig

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

awslabs/aidlc-workflows PR #253: feat(extensions): consolidated selection menu and community extensions framework

Requirements Analysis now uses one extension selection menu, while `community-extensions-index.yaml` defines a standard manifest contract used by the existing extension loader.