Skip to content

Clarify that coding-agents-prompting-flow.md is a Rosetta KB path, no… #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
YevheniiaLementova wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify that coding-agents-prompting-flow.md is a Rosetta KB path, no… #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,9 @@ Rosetta is a prompt engineering system. Prompt changes have outsized impact and

**Use the prompting flow.** The [`coding-agents-prompting-flow`](USAGE_GUIDE.md#workflows) with `coding-agents-prompt-authoring` skill helps you author, design, refactor, harden, and modernize prompt families (agents, skills, workflows, workflow phases, rules). It understands Rosetta internals. Use it with Opus 4.6 model.

Examples:
> **Note:** The path `instructions/r2/grid/workflows/coding-agents-prompting-flow.md` in the examples below is a **Rosetta knowledge base path**, not a file in this repository. The `grid` scope is an enterprise extension served via [Rosetta MCP](USAGE_GUIDE.md#plugins) and is not included in the open-source repo file tree. These example prompts require Rosetta MCP to be active so the path resolves from the knowledge base.

Examples (all require Rosetta MCP to resolve the `grid` scope from the knowledge base):

1. Refactoring old rosetta prompt to new:
```
Expand All @@ -63,7 +65,7 @@ Examples:
MUST FULLY EXECUTE `instructions/r2/grid/workflows/coding-agents-prompting-flow.md` to author a new R2 Rosetta <skill/agent/workflow/rule/prompt family> `<name>` in `grid` scope: <description of what it should be>
```

3. Using Rosetta MCP
3. Explicit KB acquisition (alternative syntax):
```
MUST ACQUIRE coding-agents-prompting-flow.md FROM KB AND FULLY EXECUTE IT to author a new R2 Rosetta <skill/agent/workflow/rule/prompt family> `<name>` in `grid` scope: <description of what it should be>
```
Expand Down
4 changes: 3 additions & 1 deletion docs/web/docs/contributing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,9 @@ Rosetta is a prompt engineering system. Prompt changes have outsized impact and

**Use the prompting flow.** The [`coding-agents-prompting-flow`](/rosetta/docs/usage-guide/#workflows) with `coding-agents-prompt-authoring` skill helps you author, design, refactor, harden, and modernize prompt families (agents, skills, workflows, workflow phases, rules). It understands Rosetta internals. Use it with Opus 4.6 model.

Examples:
> **Note:** The path `instructions/r2/grid/workflows/coding-agents-prompting-flow.md` in the examples below is a **Rosetta knowledge base path**, not a file in this repository. The `grid` scope is an enterprise extension served via [Rosetta MCP](/rosetta/docs/usage-guide/#plugins) and is not included in the open-source repo file tree. These example prompts require Rosetta MCP to be active so the path resolves from the knowledge base.

Examples (all require Rosetta MCP to resolve the `grid` scope from the knowledge base):

1. Refactoring old rosetta prompt to new:
```
Expand Down