Skip to content

fix: add steering to enforce orchestration for all code-change prompts#350

Open
SiddhJog wants to merge 1 commit into
v2_backupfrom
bugfix/steering-orchestration-enforcement
Open

fix: add steering to enforce orchestration for all code-change prompts#350
SiddhJog wants to merge 1 commit into
v2_backupfrom
bugfix/steering-orchestration-enforcement

Conversation

@SiddhJog

Copy link
Copy Markdown
Contributor

In brownfield repos, Kiro's default routing intercepts small code-change requests ("make buttons yellow", "add a grid to dashboard") and invokes its built-in context-gatherer instead of the aidlc orchestrator. The orchestration skill never gets activated.

Fix: Add an always-included steering file that tells Kiro to route ALL code-change requests through aidlc-orchestration first, regardless of workspace state.

  • Added aidlc-workflows.md with inclusion: always
  • Broadened orchestration skill description to cover small changes explicitly

In brownfield repos, Kiro's default routing intercepts small code-change
requests and invokes context-gatherer instead of aidlc orchestrator.

Fix: Add always-included steering file that routes ALL code-change
requests through aidlc-orchestration first.

- Added kiro/src/steering/aidlc-workflows.md (inclusion: always)
- Updated build to copy steering files to dist
- Broadened orchestration skill description to cover small changes
@raj-jain-aws

Copy link
Copy Markdown
Contributor

@SiddhJog - Does this happen even when the user starts their intent with "Using AIDLC, ..."? I think its okay if the user sometimes doesn't want to engage AI-DLC for their own reasons. The "Using AIDLC ...", acts as that dynamic choice.

@SiddhJog

Copy link
Copy Markdown
Contributor Author

@raj-jain-aws When the user starts with "aidlc" the orchestration skill is engaged. See your point. Holding off. lets discuss.

@raj-jain-aws

Copy link
Copy Markdown
Contributor

@SiddhJog I'm assuming this can now be closed given the latest v2 refresh? If so, pls. close.

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