Skip to content

Comments

Radius Spec Kit Prompt Agent#143

Open
brooke-hamilton wants to merge 5 commits intoradius-project:mainfrom
brooke-hamilton:brooke-hamilton/spec-kit-prompt-agent
Open

Radius Spec Kit Prompt Agent#143
brooke-hamilton wants to merge 5 commits intoradius-project:mainfrom
brooke-hamilton:brooke-hamilton/spec-kit-prompt-agent

Conversation

@brooke-hamilton
Copy link
Member

@brooke-hamilton brooke-hamilton commented Feb 7, 2026

Summary

Adds a new Copilot Chat agent (radius-spec-kit-prompt-agent) that helps contributors translate feature ideas into well-structured Spec Kit prompts. The agent acts as an expert Radius system architect, researching the codebase across all five Radius repositories and generating context-rich prompts for the /speckit.specify and /speckit.plan workflows.

What the agent does

  • Analyzes scope — Determines whether a proposed change affects CLI, APIs, resource types, recipes, or multiple components
  • Researches existing patterns — Searches the codebase for related functionality and surfaces relevant code paths, APIs, and design documents
  • Validates architectural alignment — Checks proposals against the project constitution and established conventions
  • Generates ready-to-use prompts — Outputs a markdown document in .copilot-tracking/ containing research notes and a copy-paste prompt for Spec Kit

Files changed

File Description
.github/agents/radius.speckit.prompt.agent.md Agent definition with expertise areas, responsibilities, key directory references, workflow guidance, and example interactions
.github/prompts/radius.speckit.prompt.prompt.md Prompt metadata that wires the agent into Copilot Chat
.gitignore Ignores .copilot-tracking/ so research artifacts remain local

Usage

Open the design-notes.code-workspace file to load all five Radius repositories, then invoke the agent via Copilot Chat. Describe the feature or change you want to propose, and the agent will produce a structured prompt document ready for /speckit.specify.

Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a new Copilot Chat agent and prompt wiring to help contributors turn Radius feature ideas into Spec Kit-ready prompts, with local research artifacts stored under .copilot-tracking/.

Changes:

  • Introduces a new agent definition (radius-spec-kit-prompt-agent) with workflow guidance and repo-specific research pointers.
  • Adds a Copilot prompt metadata file to expose the agent via Copilot Chat.
  • Updates .gitignore to exclude .copilot-tracking/ artifacts from commits.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 3 comments.

File Description
.gitignore Ignores .copilot-tracking/ for local-only research outputs.
.github/prompts/radius.speckit.prompt.prompt.md Adds prompt metadata to map a Copilot prompt to the new agent.
.github/agents/radius.speckit.prompt.agent.md Defines the new Radius Spec Kit prompt agent behavior, handoffs, and reference directories.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


### Radius Core System (`radius/` repository)
- **Universal Control Plane (UCP)**: The control plane that orchestrates Radius resources
- **Resource Providers**: Applications.Core, Applications.Datastores, Applications.Messaging, Applications.Dapr
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be updated to new namespaces?

Copy link
Member Author

Choose a reason for hiding this comment

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

Updated.


You have comprehensive knowledge of:

### Radius Core System (`radius/` repository)
Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about adding dynamic rp and integration with AWS resources here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Done

- **Deployment Engine**: Bicep-based deployment orchestration
- **Kubernetes Integration**: How Radius deploys to and manages Kubernetes clusters

### Related Repositories
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: missing repo - bicep-types-aws

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed, and I also added bicep-types-aws to the workspace file.

- **`design-notes/`**: Specifications, architecture decisions, and feature proposals

### Key Architectural Concepts
- **Portable Resources**: Abstract resource types that resolve to cloud-specific implementations via recipes
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we are keeping portable resources term with Radius Resoruce types going forward.

Copy link
Member Author

Choose a reason for hiding this comment

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

Removed, and I added a reference to RRTs.

- **`resource-types-contrib/`**: Community-contributed resource type definitions and recipes
- **`design-notes/`**: Specifications, architecture decisions, and feature proposals

### Key Architectural Concepts
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we add recipes and radius resource types in this list?

Copy link
Member Author

Choose a reason for hiding this comment

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

Added

- **Portable Resources**: Abstract resource types that resolve to cloud-specific implementations via recipes
- **Connections**: Declared dependencies between resources that Radius manages
- **Environments**: Logical groupings that bind recipes to resource types
- **Applications**: Top-level containers for related Radius resources
Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if this description could result into inaccuracies in the generated prompt since it isn't really a container..

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed


## Key Directories to Reference

### In `radius/` repository:
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd also add dynamicrp to this list

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed

Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
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