Skip to content

Feat/extensions#116

Open
ClintEastman02 wants to merge 5 commits intoawslabs:mainfrom
ClintEastman02:feat/extensions
Open

Feat/extensions#116
ClintEastman02 wants to merge 5 commits intoawslabs:mainfrom
ClintEastman02:feat/extensions

Conversation

@ClintEastman02
Copy link

Issue #, if available: N/A

Description of changes:

Adds the Extension Generator Skill (v1.0.0) — an IDE-agnostic, one-time skill that converts any ruleset into structured, enforceable AI-DLC extension folders. Supports compliance
frameworks (HIPAA, PCI-DSS, GDPR, etc.) via CSA CCM v4.1 normalization, as well as coding standards, business rules, architecture patterns, and team processes without CCM overhead.

Key changes:

  • Extension Generator Skill (generator-skill.md) — full generation flow: entry point selection, rule type classification, adaptive scoping questions, folder/file generation with
    universal templates, and review/approval
  • Opt-in gate (extension-generator.opt-in.md) — lightweight prompt presented during Requirements Analysis so the full skill only loads into context when the user opts in
  • CCM v4.1 reference (ccm-reference.md) — 17 domains, 207 controls, official source-of-truth registry for 14+ frameworks, loaded only for compliance/security rule types
  • Rule manifest (rule-manifest.yaml) — metadata, keyword triggers, stage mapping
  • Technical overview (EXTENSION-GENERATOR-OVERVIEW.md) — detailed documentation of the skill's architecture, flow, and Phase 2 roadmap
  • Output restructured to aidlc-docs/extensions/[category]/[standard-name]/ so multiple extensions in the same category are grouped under a shared folder

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Introduces the extension generator skill with hybrid entry points
(workflow-triggered recommended path + standalone manual path),
type-adaptive scoping questions, CCM reference split into separate
file for compliance-only loading, and extension-discovery.md tracking.
- Add extension-generator.opt-in.md to gate skill loading behind
  user consent during Requirements Analysis
- Remove redundant applicability check from generator-skill.md
  since opt-in file now handles that gate
- Change output path from [category]-[name]/ to [category]/[name]/
  to group multiple extensions under the same category folder
Copy link
Contributor

@harmjeff harmjeff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a README for this extension for users

This is an experimental feature that will allow the user to create extension rules for themselves. It is currently focused on regulatory impact, but the pattern is extensible to any internal rules creation based of documentation resources. User should be cautioned in a README that the rules created must be reviewed by the proper legal, security, & technical resources.

Add user-facing documentation explaining the experimental extension
generator, its capabilities, and important disclaimers that generated
rules must be reviewed by legal, security, and technical resources.
Avoid confusion with Claude skills by renaming all "skill" terminology
to "extension" throughout the extension generator files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants