Skip to content

Add communication style steering file#48

Open
janellearita wants to merge 1 commit intoopensearch-project:mainfrom
janellearita:add-communication-style-steering
Open

Add communication style steering file#48
janellearita wants to merge 1 commit intoopensearch-project:mainfrom
janellearita:add-communication-style-steering

Conversation

@janellearita
Copy link
Copy Markdown

Summary

Adds a communication style steering file (kiro/opensearch-launchpad/steering/communication-style.md) that applies to all Kiro interactions with the OpenSearch Launchpad power.

What it does

Sets consistent tone and formatting guidelines so Kiro responds like a teammate rather than a support bot. Key rules:

  • Keep responses concise — state the result, ask what's next
  • One question per message, no batching
  • Frame option lists as questions (no trailing "Which one?")
  • No enthusiasm theater ("Great choice!") or apology loops
  • Match the user's energy level
  • Progressive disclosure — lead with the answer, offer depth only when asked
  • Adapt to user expertise signals

Why

During testing of the Launchpad workflow, Kiro's default responses were verbose and inconsistent across phases. This steering file standardizes the communication style to improve the interactive experience, especially during the multi-phase workflow where brevity matters.

Inclusion mode

Set to always — applies automatically to every interaction without needing to be manually referenced.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Signed-off-by: Janelle <janarita@amazon.com>
@janellearita janellearita force-pushed the add-communication-style-steering branch from 9a9de44 to 1f84661 Compare March 11, 2026 20:00
Copy link
Copy Markdown
Member

@owaiskazi19 owaiskazi19 left a comment

Choose a reason for hiding this comment

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

This is a good addition for the interface. Thanks @janellearita . Added few comments

@@ -0,0 +1,210 @@
---
inclusion: always
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
inclusion: always
inclusion: auto

@@ -0,0 +1,210 @@
---
inclusion: always
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you also add a description tag before inclusion and add an one liner description for the steering file

- Asks "why" questions about architecture decisions
- Gives terse instructions

→ Be terse back. Skip basics. Go straight to implementation.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

For my understanding. What do we want to mean with Be terse back.?

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