Skip to content

feat: agent-driven setup — drop the manual steps#109

Open
DavidHache wants to merge 8 commits intoawslabs:mainfrom
DavidHache:main
Open

feat: agent-driven setup — drop the manual steps#109
DavidHache wants to merge 8 commits intoawslabs:mainfrom
DavidHache:main

Conversation

@DavidHache
Copy link

@DavidHache DavidHache commented Mar 6, 2026

Screenshot 2026-03-06 at 2 47 50 PM As AI agents get better at following instructions, it opens up simpler ways to solve problems we used to handle with scripts and commands.

Rather than maintaining platform-specific setup steps for every IDE, we now provide a single prompt and let the agent create the right config file for its environment.

Flattened aidlc-rules/ into one directory. Added SETUP.md with a two-step process: git submodule add, then paste the prompt. The agent handles the rest.

Issue #, if available:

Description of changes:

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

As AI agents get better at following instructions, it opens up simpler
ways to solve problems we used to handle with scripts and commands.

Rather than maintaining platform-specific setup steps for every IDE,
we now provide a single prompt and let the agent create the right
config file for its environment.

Flattened aidlc-rules/ into one directory. Added SETUP.md with a
two-step process: git submodule add, then paste the prompt. The agent
handles the rest.
David Hache added 3 commits March 11, 2026 10:37
…lder structure

Workshops and tests depend on the original directory names. Reverts the
flatten from 94619af while keeping the AI-driven setup approach.

- Move rule details back to aidlc-rules/aws-aidlc-rule-details/
- Move core-workflow back to aidlc-rules/aws-aidlc-rules/
- Add .aidlc/aidlc-rules/aws-aidlc-rule-details/ as first path in
  core-workflow.md resolution, keeping legacy paths as fallbacks
- Update SETUP.md, README.md, CONTRIBUTING.md for restored structure
- Add "Do Not Rename or Move" guidance to CONTRIBUTING.md
- Update submodule URL to awslabs/aidlc-workflows.git
@DavidHache DavidHache changed the title feat: agent-driven setup — flatten rules, drop the manual steps feat: agent-driven setup — drop the manual steps Mar 11, 2026
@DavidHache DavidHache requested review from a team as code owners March 12, 2026 16:05
@harmjeff
Copy link
Contributor

2 Requested changes:

  1. Add setup to the main README.md after the Kiro (top) instructions
  2. Retain the old school instructions (manual) and add the AI setup as another option, in the navigation add AI Installation as an option after Kiro with an "Experimental" prefix

@DavidHache
Copy link
Author

2 Requested changes:

1. Add setup to the main README.md after the Kiro (top) instructions

2. Retain the old school instructions (manual) and add the AI setup as another option, in the navigation add AI Installation as an option after Kiro with an "Experimental" prefix

Done.

**Updating AI-DLC** — To pull the latest rules:

```bash
git submodule update --remote .aidlc
Copy link
Contributor

Choose a reason for hiding this comment

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

Using git is nice for easy updates, but undermines the use of releases in the project to manage versions. Personally I'd prefer to direct the agent to download the latest release instead.

Copy link
Author

Choose a reason for hiding this comment

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

As this is experimental, I would suggest we stick to the head. Once it's part of the "full release" then we can move to a release branch and let the user choose sub-module or zip?

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.

As a mainline (not versioned) head it is fine. More testing is necessary to determine if this approach is universal before we reture the old onstructions.

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.

3 participants