Conversation
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
ClintEastman02
requested review from
a team,
harmjeff,
raj-jain-aws,
scottschreckengaust and
spraja08
harmjeff
left a comment
harmjeff
left a comment
There was a problem hiding this comment.
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.
harmjeff
left a comment
harmjeff
left a comment
There was a problem hiding this comment.
This meets my expectation for an experimental extension
|
@ai-ram-ramani - Could you provide your views on this from a security outcomes and accountability point of view. |
|
Per our conversation @ClintEastman02 there is a better version coming and this merge has issues we'd like to avoid. |
3 participants
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:
universal templates, and review/approval
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.