Skip to content

A programming framework for agentic AI

Merge branch 'elsa3new'

Ryan Sweet81b84eceec9a
diff --cc .gitignore
index 0da63ea87,85fa5e4e2..484de8a89
--- a/.gitignore
+++ b/.gitignore
@@@ -482,3 -482,12 +482,15 @@@ $RECYCLE.BIN
# Vim temporary swap files
*.swp
++<<<<<<< HEAD
++=======
+
+ # SQLite workflows DB
+ elsa.sqlite.*
+
+ # env files
+ .env
+
+ # ignore local elsa-core src
-elsa-core/
++elsa-core/
++>>>>>>> elsa3new
diff --cc .vscode/settings.json
index b7c2cb24a,765a2c0e3..e4c70cc4c
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@@ -1,3 -1,8 +1,12 @@@
{
++<<<<<<< HEAD
+ "dotnet.defaultSolution": "sk-dev-team.sln"
++=======
+ "dotnet.defaultSolution": "sk-dev-team.sln",
+ "azureFunctions.deploySubpath": "sk-azfunc-server/bin/Release/net7.0/publish",
+ "azureFunctions.projectLanguage": "C#",
+ "azureFunctions.projectRuntime": "~4",
+ "debug.internalConsoleOptions": "neverOpen",
+ "azureFunctions.preDeployTask": "publish (functions)"
++>>>>>>> elsa3new
}
diff --cc Elsa.SemanticKernel/Config/KernelSettings.cs
index 613c2c92e,7e549c9af..7d12f8c9b
--- a/Elsa.SemanticKernel/Config/KernelSettings.cs
+++ b/Elsa.SemanticKernel/Config/KernelSettings.cs
@@@ -4,12 -4,12 +4,19 @@@ using Microsoft.Extensions.Logging
using System.IO;
using System;
++<<<<<<< HEAD
+
++=======
++>>>>>>> elsa3new
internal class KernelSettings
{
public const string DefaultConfigFile = "config/appsettings.json";
public const string OpenAI = "OPENAI";
public const string AzureOpenAI = "AZUREOPENAI";
++<<<<<<< HEAD
++=======
+ public const int DefaultMaxRetries = 9;
++>>>>>>> elsa3new
[JsonPropertyName("serviceType")]
public string ServiceType { get; set; } = string.Empty;
diff --cc Elsa.SemanticKernel/Elsa.SemanticKernel.csproj
index 8b4fb761f,9f6e6c2ee..effef1869
--- a/Elsa.SemanticKernel/Elsa.SemanticKernel.csproj
+++ b/Elsa.SemanticKernel/Elsa.SemanticKernel.csproj
@@@ -5,11 -5,15 +5,23 @@@
<Description>
Activities for calling Semantic Kernel SDK
</Description>
++<<<<<<< HEAD
+ <PackageTags>elsa module semantic kerne activities</PackageTags>
+ </PropertyGroup>
+
+ <ItemGroup>
+ <PackageReference Include="Elsa" Version="3.0.0-rc1" />
++=======
+ <PackageTags>elsa module semantic kernel activities</PackageTags>
+ </PropertyGroup>
+
+ <ItemGroup>
+ <PackageReference Include="Elsa" Version="3.0.0-preview.552" />
+ <PackageReference Include="Elsa.Http" Version="3.0.0-preview.552" />
+ <PackageReference Include="Elsa.Workflows.Api" Version="3.0.0-preview.552" />
+ <PackageReference Include="Elsa.Workflows.Core" Version="3.0.0-preview.552" />
+ <PackageReference Include="Elsa.Workflows.Management" Version="3.0.0-preview.552" />
++>>>>>>> elsa3new
<PackageReference Include="Microsoft.Extensions.Configuration.UserSecrets" Version="7.0.0" />
<PackageReference Include="Microsoft.Extensions.Logging.Console" Version="7.0.0" />
<PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="7.0.0" />
diff --cc Elsa.SemanticKernel/NuGet.Config
index a89a1e8b5,5d2144320..42b3a4ad0
--- a/Elsa.SemanticKernel/NuGet.Config
+++ b/Elsa.SemanticKernel/NuGet.Config
@@@ -3,7 -3,7 +3,11 @@@
<packageSources>
<clear/>
++<<<<<<< HEAD
+ <add key="NuGet official package source" value="https://api.nuget.org/v3/index.json" />
++=======
+ <!--add key="NuGet official package source" value="https://api.nuget.org/v3/index.json" /-->
++>>>>>>> elsa3new
<add key="Jint prereleases" value="https://www.myget.org/F/jint/api/v3/index.json" />
<add key="Elsa prereleases" value="https://f.feedz.io/elsa-workflows/elsa-3/nuget/index.json" />
</packageSources>
diff --cc README.md
index c12517431,730687f1f..7485c951d
--- a/README.md
+++ b/README.md
@@@ -1,67 -1,132 +1,197 @@@
++<<<<<<< HEAD
+# sk-dev-team
+# Build a Virtual AI Dev Team using Semantic Kernel Skills
+## Status
+This is a nascent project - we will use the README to describe the project's intent - as we build it out we will document what exists and eventually move roadmap/intent to the discussion.
+
+## Trying it out
+Currently the project can take as input a brief description of a desired application, and as output can create the project files for that application, using a PM skill, a Dev Lead Planning Skill, and a Developer Skill.
+
+The easiest way to run the project is in Codespaces. Codespaces will start a qdrant instance for you, and will inject all the necessary secrets into environment variables.
+1. Create a new codespace from the *code* button on the main branch.
+2. Once the code space setup is finished, from the terminal:
+```
+> cd cli
+cli> dotnet build
+cli> dotnet run --file util/ToDoListSamplePrompt.txt do it
+```
+You will find the output in the *output/* directory.
+
+# Goal
+From a natural language specification, set out to integrate a team of AI copilot skills into your team’s dev process, either for discrete tasks on an existing repo (unit tests, pipeline expansions, PRs for specific intents), developing a new feature, or even building an application from scratch. Starting from an existing repo and a broad statement of intent, work with multiple AI copilot dev skills, each of which has a different emphasis - from architecture, to task breakdown, to plans for individual tasks, to code output, code review, efficiency, documentation, build, writing tests, setting up pipelines, deployment, integration tests, and then validation.
+The system will present a view that facilitates chain-of-thought coordination across multiple trees of reasoning with the dev team skills.
+## Proposed UX
+* Possible UI: Start with an existing repo (GH or ADO), either populated or empty, and API Keys / config for access – once configured / loaded split view between three columns:
+** Settings/History/Tasks (allows browsing into each of the chats with a copilot dev team role) | [Central Window Chat interface with Copilot DevTeam] | Repo browsing/editing
+** Alternate interface will be via VS Code plugin/other IDE plugins, following the plugin idiom for each IDE
+** Settings include teams channel for conversations, repo config and api keys, model config and api keys, and any desired prompt template additions
+* CLI: start simple with a CLI that can be passed a file as prompt input and takes optional arguments as to which skills to invoke
+* User begins with specifying a repository and then statement of what they want to accomplish, natural language, as simple or as detailed as needed.
+** SK DevTeam skill will use dialog to refine the intent as needed, returns a plan, proposes necessary steps
+** User approves the plan or gives feedback, requests iteration
+** Plan is parceled out to the appropriate further skills
+** Eg, for a new app:
+*** Architecture is passed to DevLead skill gives plan/task breakdown.
+*** DevLead breaks down tasks into smaller tasks, each of these is fed to a skill to decide if it is a single code module or multiple
+*** Each module is further fed to a dev lead to break down again or specify a prompt for a coder
+*** Each code module prompt is fed to a coder
+*** Each module output from a coder is fed to a code reviewer (with context, specific goals)
+*** Each reviewer proposes changes, which result in a new prompt for the original coder
+*** Changes are accepted by the coder
+*** Each module fed to a builder
+*** If it doesn’t build sent back to review
+*** (etc)
+## Proposed Architecture
+* SK Kernel Service – ASP.NET Core Service with REST API
+* SK Skills:
+** PM Skill – generates pot, word docs, describing app,
+** Designer Skill – mockups?
+** Architect Skill – proposes overall arch
+** DevLead Skill – proposes task breakdown
+** CoderSkill – builds code modules for each task
+** ReviewerSkill – improves code modules
+** TestSkill – writes tests
+** Etc
+* Web app: prompt front end and wizard style editor of app
+* Build service sandboxes – using branches and actions/pipelines 1st draft; Alternate – ephemeral build containers
+* Logging service streaming back to azure logs analytics, app insights, and teams channel
+* Deployment service – actions/pipelines driven
+* Azure Dev Skill – lean into azure integrations – crawl the azure estate to inventory a tenant’s existing resources to memory and help inform new code. Eg: you have a large azure sql estate? Ok, most likely you want to wire your new app to one of those dbs, etc….
++=======
+
+ # sk-dev-team
+
+ # Build a Virtual AI Dev Team using Semantic Kernel Skills
+
+ ## Status
+
+ This is a nascent project - we will use the README to describe the project's intent - as we build it out we will document what exists and eventually move roadmap/intent to the discussion.
+
+ ## Trying it out
+
+ ### Elsa.SemanticKernel
+
+ SemanticKernel Activity Provider for Elsa Workflows 3.x
+
+ The project supports running [Microsoft Semantic Kernel](https://github.com/microsoft/semantic-kernel) Skills as workflows using [Elsa Workflows](https://v3.elsaworkflows.io). You can build the workflows as .NET code or in the visual designer.
+ To run the designer:
+
+ ```bash
+ > cd WorkflowsApp
+ > cp .env_example .env
+ # Edit the .env file to choose your AI model, add your API Endpoint, and secrets.
+ > bash .env
+ > dotnet build
+ > dotnet run
+ # Open browser to the URI in the console output
+ ```
+
+ By Default you can use "admin" and "password" to login. Please review [Workflow Security](https://v3.elsaworkflows.io/docs/installation/aspnet-apps-workflow-server) for into on securing the app, using API tokens, and more.
+
+ To [invoke](https://v3.elsaworkflows.io/docs/guides/invoking-workflows) a workflow, first it must be "Published". If your workflow has a trigger activity, you can use that. When your workflow is ready, click the "Publish" button. You can also execute the workflow using the API. Then, find the Workflow Definition ID. From a command line, you can use "curl":
+
+ ```bash
+ > curl --location 'https://localhost:5001/elsa/api/workflow-definitions/{workflow_definition_id}/execute' \
+ --header 'Content-Type: application/json' \
+ --header 'Authorization: ApiKey {api_key}' \
+ --data '{
+ }'
+ ```
+
+ Once you have the app runing locally, you can login (admin/password - see the [Elsa Workflows](https://v3.elsaworkflows.io) for info about securing). Then you can click "new workflow" to begin building your workflow with semantic kernel skills.
+
+ 1. Drag workflow Activity blocks into the designer, and examine the settings.
+ 2. Connect the Activities to specify an order of operations.
+ 3. You can use Workfflow Variables to pass state between activities.
+ 1. Create a Workflow Variable, "MyVariable"
+ 2. Click on the Activity that you want to use to populate the variable.
+ 3. In the Settings box for the Activity, Click "Output"
+ 4. Set the "Output" to the variable chosen.
+ 5. Click the Activity that will use the variable. Click on "Settings".
+ 6. Find the text box representing the variable that you want to populate, in this case usually "input".
+ 7. Click the "..." widget above the text box, and select "javascript"
+ 8. Set the value of the text box to
+
+ ```javascript
+ `${getMyVariable()}`
+ ```
+
+ 9. Run the workflow.
+
+ ## Via CLI
+
+ The easiest way to run the project is in Codespaces. Codespaces will start a qdrant instance for you.
+
+ 1. Create a new codespace from the *code* button on the main branch.
+ 2. Once the code space setup is finished, from the terminal:
+
+ ```bash
+ > cd cli
+ cli> cp ../WorkflowsApp/.env_example .
+ # Edit the .env file to choose your AI model, add your API Endpoint, and secrets.
+ cli> bash .env
+ cli> dotnet build
+ cli> dotnet run --file util/ToDoListSamplePrompt.txt do it
+ ```
+
+ You will find the output in the *output/* directory.
+
+ # Goal
+
+ From a natural language specification, set out to integrate a team of AI copilot skills into your team’s dev process, either for discrete tasks on an existing repo (unit tests, pipeline expansions, PRs for specific intents), developing a new feature, or even building an application from scratch. Starting from an existing repo and a broad statement of intent, work with multiple AI copilot dev skills, each of which has a different emphasis - from architecture, to task breakdown, to plans for individual tasks, to code output, code review, efficiency, documentation, build, writing tests, setting up pipelines, deployment, integration tests, and then validation.
+ The system will present a view that facilitates chain-of-thought coordination across multiple trees of reasoning with the dev team skills.
+
+ ## Proposed UX
+
+ * Possible UI: Start with an existing repo (GH or ADO), either populated or empty, and API Keys / config for access – once configured / loaded split view between three columns:
+ * Settings/History/Tasks (allows browsing into each of the chats with a copilot dev team role) | [Central Window Chat interface with Copilot DevTeam] | Repo browsing/editing
+ * Alternate interface will be via VS Code plugin/other IDE plugins, following the plugin idiom for each IDE
+ * Settings include teams channel for conversations, repo config and api keys, model config and api keys, and any desired prompt template additions
+ * CLI: start simple with a CLI that can be passed a file as prompt input and takes optional arguments as to which skills to invoke
+ * User begins with specifying a repository and then statement of what they want to accomplish, natural language, as simple or as detailed as needed.
+ * SK DevTeam skill will use dialog to refine the intent as needed, returns a plan, proposes necessary steps
+ * User approves the plan or gives feedback, requests iteration
+ * Plan is parceled out to the appropriate further skills
+ * Eg, for a new app:
+ * Architecture is passed to DevLead skill gives plan/task breakdown.
+ * DevLead breaks down tasks into smaller tasks, each of these is fed to a skill to decide if it is a single code module or multiple
+ * Each module is further fed to a dev lead to break down again or specify a prompt for a coder
+ * Each code module prompt is fed to a coder
+ * Each module output from a coder is fed to a code reviewer (with context, specific goals)
+ * Each reviewer proposes changes, which result in a new prompt for the original coder
+ * Changes are accepted by the coder
+ * Each module fed to a builder
+ * If it doesn’t build sent back to review
+ * (etc)
+
+ ## Proposed Architecture
+
+ * SK Kernel Service – ASP.NET Core Service with REST API
+ * SK Skills:
+ * PM Skill – generates pot, word docs, describing app,
+ * Designer Skill – mockups?
+ * Architect Skill – proposes overall arch
+ * DevLead Skill – proposes task breakdown
+ * CoderSkill – builds code modules for each task
+ * ReviewerSkill – improves code modules
+ * TestSkill – writes tests
+ * Etc
+ * Web app: prompt front end and wizard style editor of app
+ * Build service sandboxes – using branches and actions/pipelines 1st draft; Alternate – ephemeral build containers
+ * Logging service streaming back to azure logs analytics, app insights, and teams channel
+ * Deployment service – actions/pipelines driven
+ * Azure Dev Skill – lean into azure integrations – crawl the azure estate to inventory a tenant’s existing resources to memory and help inform new code. Eg: you have a large azure sql estate? Ok, most likely you want to wire your new app to one of those dbs, etc….
++>>>>>>> elsa3new
# Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
++<<<<<<< HEAD
+the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
++=======
+ the rights to use your contribution. For details, visit <https://cla.opensource.microsoft.com>.
++>>>>>>> elsa3new
When you submit a pull request, a CLA bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions
@@@ -81,9 -146,9 +211,15 @@@ see the [LICENSE](LICENSE) file, and gr
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
++<<<<<<< HEAD
+Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
+
+Privacy information can be found at https://privacy.microsoft.com/en-us/
++=======
+ Microsoft's general trademark guidelines can be found at <http://go.microsoft.com/fwlink/?LinkID=254653>.
+
+ Privacy information can be found at <https://privacy.microsoft.com/en-us/>
++>>>>>>> elsa3new
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents,
or trademarks, whether by implication, estoppel or otherwise.
diff --cc cli/Program.cs
index 0479aaf35,977cce0ff..96a0d84b1
--- a/cli/Program.cs
+++ b/cli/Program.cs
@@@ -7,7 -7,8 +7,12 @@@ using Microsoft.SemanticKernel.Connecto
using Microsoft.SemanticKernel.Memory;
using Microsoft.SemanticKernel.Orchestration;
using Microsoft.SemanticKernel.Reliability;
++<<<<<<< HEAD
+using skills;
++=======
+ using Microsoft.SKDevTeam;
+
++>>>>>>> elsa3new
class Program
{
@@@ -34,7 -35,7 +39,11 @@@
var pmCommand = new Command("pm", "Commands for the PM team");
var pmReadmeCommand = new Command("readme", "Produce a Readme for a given input");
++<<<<<<< HEAD
+ pmReadmeCommand.SetHandler(async (file, maxRetry) => await CallWithFile<string>(nameof(PM), PM.Readme , file.FullName, maxRetry), fileOption, maxRetryOption);
++=======
+ pmReadmeCommand.SetHandler(async (file, maxRetry) => await CallWithFile<string>(nameof(PM), PM.Readme, file.FullName, maxRetry), fileOption, maxRetryOption);
++>>>>>>> elsa3new
var pmBootstrapCommand = new Command("bootstrap", "Bootstrap a project for a given input");
pmBootstrapCommand.SetHandler(async (file, maxRetry) => await CallWithFile<string>(nameof(PM), PM.BootstrapProject, file.FullName, maxRetry), fileOption, maxRetryOption);
@@@ -51,7 -52,7 +60,11 @@@
var devPlanCommand = new Command("plan", "Implement the module for a given input");
devPlanCommand.SetHandler(async (file, maxRetry) => await CallWithFile<string>(nameof(Developer), Developer.Implement, file.FullName, maxRetry), fileOption, maxRetryOption);
devCommand.AddCommand(devPlanCommand);
++<<<<<<< HEAD
+
++=======
+
++>>>>>>> elsa3new
rootCommand.AddCommand(pmCommand);
rootCommand.AddCommand(devleadCommand);
rootCommand.AddCommand(devCommand);
@@@ -67,7 -68,7 +80,11 @@@
Console.WriteLine($"Using output directory: {outputPath}");
++<<<<<<< HEAD
+ var readme = await CallWithFile<string>(nameof(PM), PM.Readme , file, maxRetry);
++=======
+ var readme = await CallWithFile<string>(nameof(PM), PM.Readme, file, maxRetry);
++>>>>>>> elsa3new
string readmeFile = Path.Combine(outputPath.FullName, "README.md");
await SaveToFile(readmeFile, readme);
Console.WriteLine($"Saved README to {readmeFile}");
@@@ -83,12 -84,13 +100,21 @@@
var implementationTasks = plan.steps.SelectMany(
(step) => step.subtasks.Select(
++<<<<<<< HEAD
+ async (subtask) => {
++=======
+ async (subtask) =>
+ {
++>>>>>>> elsa3new
Console.WriteLine($"Implementing {step.step}-{subtask.subtask}");
var implementationResult = string.Empty;
while (true)
{
++<<<<<<< HEAD
+ try
++=======
+ try
++>>>>>>> elsa3new
{
implementationResult = await CallFunction<string>(nameof(Developer), Developer.Implement, subtask.LLM_prompt, maxRetry);
break;
@@@ -105,7 -107,8 +131,12 @@@
}
await sandboxSkill.RunInDotnetAlpineAsync(implementationResult);
await SaveToFile(Path.Combine(outputPath.FullName, $"{step.step}-{subtask.subtask}.sh"), implementationResult);
++<<<<<<< HEAD
+ return implementationResult; }));
++=======
+ return implementationResult;
+ }));
++>>>>>>> elsa3new
await Task.WhenAll(implementationTasks);
}
@@@ -115,8 -118,8 +146,13 @@@
}
public static async Task<T> CallWithFile<T>(string skillName, string functionName, string filePath, int maxRetry)
++<<<<<<< HEAD
+ {
+ if(!File.Exists(filePath))
++=======
+ {
+ if (!File.Exists(filePath))
++>>>>>>> elsa3new
throw new FileNotFoundException($"File not found: {filePath}", filePath);
var input = File.ReadAllText(filePath);
return await CallFunction<T>(skillName, functionName, input, maxRetry);
@@@ -173,10 -176,11 +209,19 @@@
var answer = await kernel.RunAsync(context, function).ConfigureAwait(false);
var result = typeof(T) != typeof(string) ? JsonSerializer.Deserialize<T>(answer.ToString()) : (T)(object)answer.ToString();
//Console.WriteLine(answer);
++<<<<<<< HEAD
++=======
+
++>>>>>>> elsa3new
return result;
}
}
public static class PM { public static string Readme = "Readme"; public static string BootstrapProject = "BootstrapProject"; }
++<<<<<<< HEAD
+public static class DevLead { public static string Plan="Plan"; }
+public static class Developer { public static string Implement="Implement"; public static string Improve="Improve";}
++=======
+ public static class DevLead { public static string Plan = "Plan"; }
+ public static class Developer { public static string Implement = "Implement"; public static string Improve = "Improve"; }
++>>>>>>> elsa3new
diff --cc sk-azfunc-server/ExecuteFunctionEndpoint.cs
index 6f54bc5e5,b4850eff2..fabf87fff
--- a/sk-azfunc-server/ExecuteFunctionEndpoint.cs
+++ b/sk-azfunc-server/ExecuteFunctionEndpoint.cs
@@@ -6,7 -6,8 +6,12 @@@ using Microsoft.Azure.WebJobs.Extension
using Microsoft.SemanticKernel;
using Microsoft.SemanticKernel.Orchestration;
using Models;
++<<<<<<< HEAD
+using skills;
++=======
+ using Microsoft.SKDevTeam;
+
++>>>>>>> elsa3new
public class ExecuteFunctionEndpoint
{
@@@ -35,6 -36,10 +40,13 @@@
try
{
var functionRequest = await JsonSerializer.DeserializeAsync<ExecuteFunctionRequest>(requestData.Body, s_jsonOptions).ConfigureAwait(false);
++<<<<<<< HEAD
++=======
+ if (functionRequest == null)
+ {
+ return await CreateResponseAsync(requestData, HttpStatusCode.BadRequest, new ErrorResponse() { Message = $"Invalid request body." }).ConfigureAwait(false);
+ }
++>>>>>>> elsa3new
var skillConfig = SemanticFunctionConfig.ForSkillAndFunction(skillName, functionName);
var function = _kernel.CreateSemanticFunction(skillConfig.PromptTemplate, skillConfig.Name, skillConfig.SkillName,
diff --cc skills/DevLead.cs
index 9ef4b92a4,fd7790399..028f4b7ec
--- a/skills/DevLead.cs
+++ b/skills/DevLead.cs
@@@ -1,4 -1,4 +1,8 @@@
++<<<<<<< HEAD
+namespace skills;
++=======
+ namespace Microsoft.SKDevTeam;
++>>>>>>> elsa3new
public static class DevLead {
public static SemanticFunctionConfig Plan = new SemanticFunctionConfig
{
@@@ -9,7 -9,42 +13,46 @@@
For each step or module then break down the steps or subtasks required to complete that step or module.
For each subtask write an LLM prompt that would be used to tell a model to write the coee that will accomplish that subtask. If the subtask involves taking action/running commands tell the model to write the script that will run those commands.
In each LLM prompt restrict the model from outputting other text that is not in the form of code or code comments.
++<<<<<<< HEAD
+ Please output a JSON data structure with a list of steps and a description of each step, and the steps or subtasks that each requires, and the LLM prompts for each subtask.
++=======
+ Please output a JSON array data structure with a list of steps and a description of each step, and the steps or subtasks that each requires, and the LLM prompts for each subtask.
+ Example:
+ [
+ {
+ "step": "Step 1",
+ "description": "This is the first step",
+ "subtasks": [
+ {
+ "subtask": "Subtask 1",
+ "description": "This is the first subtask",
+ "prompt": "Write the code to do the first subtask"
+ },
+ {
+ "subtask": "Subtask 2",
+ "description": "This is the second subtask",
+ "prompt": "Write the code to do the second subtask"
+ }
+ ]
+ },
+ {
+ "step": "Step 2",
+ "description": "This is the second step",
+ "subtasks": [
+ {
+ "subtask": "Subtask 1",
+ "description": "This is the first subtask",
+ "prompt": "Write the code to do the first subtask"
+ },
+ {
+ "subtask": "Subtask 2",
+ "description": "This is the second subtask",
+ "prompt": "Write the code to do the second subtask"
+ }
+ ]
+ }
+ ]
++>>>>>>> elsa3new
Do not output any other text.
Input: {{$input}}
{{$wafContext}}
diff --cc skills/Developer.cs
index 5f5cb3a94,0d072ed56..ae453ac7a
--- a/skills/Developer.cs
+++ b/skills/Developer.cs
@@@ -1,5 -1,5 +1,9 @@@
++<<<<<<< HEAD
+namespace skills;
++=======
+ namespace Microsoft.SKDevTeam;
++>>>>>>> elsa3new
public static class Developer {
public static SemanticFunctionConfig Implement = new SemanticFunctionConfig
{
diff --cc skills/PM.cs
index 4f91c420e,2eaca6610..7de6134b6
--- a/skills/PM.cs
+++ b/skills/PM.cs
@@@ -1,4 -1,4 +1,8 @@@
++<<<<<<< HEAD
+namespace skills;
++=======
+ namespace Microsoft.SKDevTeam;
++>>>>>>> elsa3new
public static class PM
{
public static SemanticFunctionConfig BootstrapProject = new SemanticFunctionConfig
diff --cc skills/SemanticFunctionConfig.cs
index 52f22e363,300ef3b59..ef5bc3fb7
--- a/skills/SemanticFunctionConfig.cs
+++ b/skills/SemanticFunctionConfig.cs
@@@ -1,4 -1,4 +1,8 @@@
++<<<<<<< HEAD
+namespace skills;
++=======
+ namespace Microsoft.SKDevTeam;
++>>>>>>> elsa3new
public class SemanticFunctionConfig
{
@@@ -14,9 -14,11 +18,17 @@@
public static SemanticFunctionConfig ForSkillAndFunction(string skillName, string functionName) =>
(skillName, functionName) switch
{
++<<<<<<< HEAD
+ (nameof(PM), nameof(PM.BootstrapProject)) => PM.BootstrapProject,
+ (nameof(PM), nameof(PM.Readme)) => PM.Readme,
+ (nameof(DevLead), nameof(DevLead.Plan)) => DevLead.Plan,
++=======
+ (nameof(Chat), nameof(Chat.ChatCompletion)) => Chat.ChatCompletion,
+ (nameof(PM), nameof(PM.BootstrapProject)) => PM.BootstrapProject,
+ (nameof(PM), nameof(PM.Readme)) => PM.Readme,
+ (nameof(DevLead), nameof(DevLead.Plan)) => DevLead.Plan,
+ (nameof(CodeExplainer), nameof(CodeExplainer.Explain)) => CodeExplainer.Explain,
++>>>>>>> elsa3new
(nameof(Developer), nameof(Developer.Implement)) => Developer.Implement,
(nameof(Developer), nameof(Developer.Improve)) => Developer.Improve,
_ => throw new ArgumentException($"Unable to find {skillName}.{functionName}")
diff --cc skills/skills.csproj
index 140c3454d,eb4501ad2..a70e9b7f9
--- a/skills/skills.csproj
+++ b/skills/skills.csproj
@@@ -4,7 -4,6 +4,10 @@@
<TargetFramework>net7.0</TargetFramework>
<ImplicitUsings>enable</ImplicitUsings>
<Nullable>enable</Nullable>
++<<<<<<< HEAD
+ <RootNamespace>skills</RootNamespace>
++=======
++>>>>>>> elsa3new
</PropertyGroup>
<ItemGroup>