GUTDODP

Author: edburns

1917-java-embed-rust-cli-runtime-remove-before-merge/1917-embed-cli-runtime-ignorance-reduction-plan.md

@@ -0,0 +1 @@
+Lorem ipsum.

1917-java-embed-rust-cli-runtime-remove-before-merge/20260721-prompts.md

@@ -0,0 +1,245 @@
+# DAY: 2026-07-21
+
+## dd-3028098-rust
+
+### 19:25 Prompt
+
+### Goal
+
+In this session, we are creating a skill to create an ignorance reduction plan given an arbitrary initial prompt. 
+
+The skill must be called `shepherd-task-create-ignorance-reduction-plan`.
+
+### Context
+
+The structure and style of the plan must follow these already-completed examples:
+
+1. `copilot-sdk-01/1682-java-tool-ergonomics-prompts-remove-before-merge/dd-3018003-ignorance-reduction-for-implementation-plan.md`
+
+2. `copilot-sdk-02/1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md`
+
+3. `BRK-206-01/dd-3017826-java-real-estate-demo-remove-before-merge/dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md`
+
+4. `BRK-206-02/28-python-agent-demo-remove-before-merge/28-python-agent-demo-ignorance-reduction-plan.md`
+
+Now, when I say "already-completed examples" the skill we are creating will cause a new ignorance reduction plan to be created, along the lines of the above examples, but the section "Ignorance reduction: questions to answer before writing code" will have empty **Resolution:** sections for each **Question:**.
+
+This is why I call it an ignorance reduction plan. It is a plan for reducing ignorance. When the plan is created, there is a lot of ignorance. The act of filling out the plan is the act of reducing ignorance about building the thing described in the plan.
+
+Embed these examples by value in the skill. Refer so the party executing the skill has a very solid understanding of what a good ignorance reduction plan looks like
+
+For all those previous plans, they started out with empty **Resolution:** sections and the human expert filled in each one with an actionable answer. Occasionally the answers would produce engineering "spike" work, which would reside in the same directory as the plan.
+
+### How the skill will be invoked
+
+Here is an example of how I envision invoking the skill
+
+<invocation-example-01>
+
+Review the chat history in `copilot-sdk/1682-java-tool-ergonomics-prompts-remove-before-merge/20260615-prompts.md`.
+
+Most important is the content within the XML element `<philosophical-difference />`
+
+Also important is the content within the XML element `<annotation-processor />`
+
+Use `gh` to open and read and understand any issue or PR links to https://github.com/github/copilot-sdk.
+
+Read and understand the ADR in `java/docs/adr/adr-005-tool-definition.md`. 
+
+We're not yet ready to ask you to write a `copilot --yolo` ready plan to do the work. We need to break it down better.
+
+Invoke the `shepherd-task-create-ignorance-reduction-plan` skill to create an ignorance reduction plan with this filename `copilot-sdk/1917-java-embed-rust-cli-runtime-remove-before-merge/1917-embed-cli-runtime-ignorance-reduction-plan.md` that is a human-targeted plan for how to proceed with the implementation of the `@CopilotTool` ergonomics improvement.
+
+- At a high level, I know we'll need to define the 
+
+   - `@CopilotTool` annotation, with `@CopilotExperimental`.
+
+   - The annotation processor that makes the `@CopilotTool` annotation work.
+
+   - Some way to "register" a tool. A Java idiomatic way of this in C#
+
+      ```C#
+      CopilotTool.DefineTool(SetCurrentPhase),
+      CopilotTool.DefineTool(ReportIntent, new() { OverridesBuiltInTool = true }),
+      CopilotTool.DefineTool(database.SearchProperties),
+      ```
+
+      - **MAYBE** something like this:
+
+         ```
+         // Registration: scan an object for @CopilotTool methods
+         var tools = ToolDefinition.fromObject(myToolsInstance);
+         ```
+
+      - I say maybe, because I'm not exactly sure how LangChain4J does it. Also, I've been told that micronaut also has a similar thing. I have added the folders `langchain4j-00-main` and `micronaut-core-00` to this VS Code project for reference.
+      
+Break the work down into phases. Note, we've already done these first two phases.
+
+1. ✅ Define the problem and make an architectural decision, recorded in an ADR.
+
+2. ✅ Verify the existing way works in Java. (This work is proceeding but as the human DRI, I am confident it will complete successfully.)
+
+</invocation-example-01>
+
+<invocation-example-02>
+
+Look at `copilot-sdk-01/1682-java-tool-ergonomics-prompts-remove-before-merge/dd-3018003-ignorance-reduction-for-implementation-plan.md`. This is the ignorance reduction plan for the initial ergonomic tools feature.
+
+We have now completed the analogous Phase 1.
+
+Using the `dd-3018003` plan as a guide, map out what we've been calling the "lambda lane" but don't call it that. Call it tool-as-lambda.
+
+Invoke the `shepherd-task-create-ignorance-reduction-plan` skill to create an ignorance reduction plan with this filename `1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md`.
+
+</invocation-example-02>
+
+<invocation-example-03>
+
+#### Overview and Goal
+
+In this multi-day campaign I intend to create a Java version of the Blazor app in `src/AgentOrchestrator` in this repository. The point of the demo is to show off the use of the Copilot SDK for C#. Read the file `BRK-206-00/docs/copilot-sdk-features.md` to understand how the demo uses the C# SDK features. Read the file `BRK-206-00/dd-3017826-java-real-estate-demo-remove-before-merge/dd-3014541-csharp-demo-detailed-notes.md` to understand how a human traverses and runs the existing C# demo.
+
+Our goal is to make an analogous demo using the Copilot SDK for Java. Recent enhancements to the Java SDK present in version 1.0.7-SNAPSHOT have added an ergonomic tools API analogous to the one shown in C#. The monorepo for Copilot SDK is available in the folder `copilot-sdk`. Read `copilot-sdk/java/docs/adr/adr-005-tool-definition.md` and `copilot-sdk/java/docs/adr/adr-006-tool-definition-inline.md` to understand the ergonomoc tools API.
+
+#### Known details
+
+The Java version will have at least the following dependencies. We can and will, of course, add more to get the job done. But I try to favor open standard solutions that separate interface from implementation, such as Jakarta EE and JCP, rather than de-factor proprietary solutions such as Spring. I realize that Copilot SDK for Java itself is proprietary and does not separate interface from implementation. Correcting this problem is a separate campaign.
+
+#### Known dependencies
+
+- Jakarta EE 11.
+- PrimeFaces 15.0.16.
+- OpenLiberty 26.0.0.5.
+- Copilot SDK for Java 1.0.7-SNAPSHOT (already installed in local maven repository).
+
+Read `BRK-206-00/docs/primefaces-research.md` for prior research on using PrimeFaces in this campaign.
+
+#### The request
+
+I need you to map out a multi-day implementation plan similar to the following plans `copilot-sdk-01/1682-java-tool-ergonomics-prompts-remove-before-merge/dd-3018003-ignorance-reduction-for-implementation-plan.md` and `copilot-sdk-02/1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md`. Note that these directories have been added to the project. These plans have structures that have proven successful in a multi-day agentic aided development campaign.
+
+Invoke the `shepherd-task-create-ignorance-reduction-plan` skill to create an ignorance reduction plan with this filename `BRK-206-00/dd-3017826-java-real-estate-demo-remove-before-merge/dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md`.
+
+</invocation-example-03>
+
+<invocation-example-04>
+
+The file `BRK206-01/dd-3017826-java-real-estate-demo-remove-before-merge/dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md` is the ignorance reduction and implementation plan to create a Java version of the Blazor app in `src/AgentOrchestrator` in this repository.
+
+In this campaign, I want to create an analogous Python version.
+
+The directory `C:\Users\edburns\workareas\BRK206-02\src\python_agent_orchestrator` is a python venv project to contain this Python implementation.
+
+Invoke the `shepherd-task-create-ignorance-reduction-plan` skill to create an ignorance reduction plan with this filename `BRK-206-02/28-python-agent-demo-remove-before-merge/28-python-agent-demo-ignorance-reduction-plan.md`.
+
+
+✅✅✅At this point, only do the phases **before** Phase 1.✅✅✅
+
+❌❌❌Do not do anything for sections from "Completed Phases" through the end of the document.❌❌❌
+
+
+</invocation-example-04>
+
+In all invocation examples, assume the LLM already has sufficient context loaded so that it can reason about what will be needed in the plan. ✅✅✅It is very important that there is enough knowledge in the context so that very solid questions can be formed for the "Ignorance reduction: questions to answer before writing code" section.
+
+### 19:37 Response
+
+Thought for 5s
+The user wants me to create a skill called `shepherd-task-create-ignorance-reduction-plan`. Let me first look at the example ignorance reduction plans to understand their structure, then create the skill file.
+Let me look at the examples and understand the skill file format used in this environment.
+
+Let me first examine the example ignorance reduction plans and existing skill files to understand the structure.
+
+Shell Find ignorance reduction plan files 6 lines…
+find /home/edburns/workareas -name "*.md" | grep -i "ignorance-reduction" | head -20
+Shell Find existing skill files 15 lines…
+find /home/edburns/workareas/copilot-sdk -name "*.skill.md" -o -name "*.skill.yml" | head -20; find /home/edburns …
+
+Read SKILL.md L1:50 (50 lines read)
+Read dd-3018003-ignorance-reduction-for-implementation-plan.md 1 line read
+Read 1810-ignorance-reduction-for-implementation-plan.md 1 line read
+Read dd-3018003-ignorance-reduction-for-implementation-plan.md L1:100 (100 lines read)
+Read 1810-ignorance-reduction-for-implementation-plan.md L1:100 (100 lines read)
+Read dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md L1:100 (100 lines read)
+Read 28-python-agent-demo-ignorance-reduction-plan.md L1:100 (100 lines read)
+Read dd-3018003-ignorance-reduction-for-implementation-plan.md L100:200 (101 lines read)
+Read 1810-ignorance-reduction-for-implementation-plan.md L100:200 (101 lines read)
+Read dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md L100:200 (101 lines read)
+Read 28-python-agent-demo-ignorance-reduction-plan.md L100:200 (101 lines read)
+
+Now let me see the later sections of these plans to understand the full structure including implementation phases:
+
+Read dd-3018003-ignorance-reduction-for-implementation-plan.md L200:350 (150 lines read)
+Read 28-python-agent-demo-ignorance-reduction-plan.md L200:350 (150 lines read)
+Read dd-3018003-ignorance-reduction-for-implementation-plan.md L340:500 (161 lines read)
+
+Now I have a solid understanding of the structure. Let me also look at the existing skill structure to understand the SKILL.md format:
+
+Read SKILL.md L1:20 (20 lines read)
+Read SKILL.md L1:30 (29 lines read)
+
+Now I have everything I need. Let me create the skill:
+
+Shell Create skill directory 1 line…
+mkdir -p /home/edburns/.copilot/skills/shepherd-task-create-ignorance-reduction-plan
+
+Create SKILL.md +566
+
+The skill has been created at `/home/edburns/.copilot/skills/shepherd-task-create-ignorance-reduction-plan/SKILL.md`.
+
+It includes:
+
+- 3 embedded examples (Java `@CopilotTool`, Java Real Estate Demo, Python Agent Demo) showing the full structure with filled-in resolutions so the executing LLM understands quality expectations
+- Clear instructions that generated plans must have empty Resolution sections
+- Quality principles for question formulation (specificity, code sketches, tables, spikes, recommendations)
+- Anti-patterns to avoid
+- A 4-step procedure (verify context → identify structure → generate plan → confirm)
+
+The skill will appear as `shepherd-task-create-ignorance-reduction-plan` in your available skills list on next session load.
+
+### 19:38 Prompt
+
+Look at the file `awesome-copilot-00/plugins/shepherd-task/scripts/install-task-shepherd.ps1` and its Bash counterpart.
+
+I just added a new skill to the shepherd-task suite `/home/edburns/.copilot/skills/shepherd-task-create-ignorance-reduction-plan`. Modify the installer and uninstaller scripts to also install/uninstall this skill. Make sure to get all the contents.
+
+### 19:41 Response
+
+Thought for 1s
+Let me look at the installer script and its bash counterpart, plus the uninstaller scripts.
+
+Shell List shepherd-task scripts 15 lines…
+find /home/edburns/workareas/awesome-copilot-00/plugins/shepherd-task/scripts -type f | sort
+
+List directory ~/.copilot/skills/shepherd-task-create-ignorance-reduction-plan 1 file found
+Read install-task-shepherd.ps1 64 lines read
+Read install-task-shepherd.sh 61 lines read
+Read uninstall-task-shepherd.ps1 42 lines read
+Read uninstall-task-shepherd.sh 40 lines read
+Read SKILL.md 1 line read
+
+The SKILL.md is large — let me check if the skill source also exists in the repo's `skills/` directory (where the installer copies from):
+
+Shell Check repo skills directory 6 lines…
+ls -d /home/edburns/workareas/awesome-copilot-00/skills/shepherd-task-* 2>/dev/null
+
+Good — the skill exists in the repo. Now I'll add `shepherd-task-create-ignorance-reduction-plan` to all four scripts:
+
+Edit install-task-shepherd.ps1 +1
+Edit install-task-shepherd.sh +1
+Edit uninstall-task-shepherd.ps1 +1
+Edit uninstall-task-shepherd.sh +1
+
+Done. I added `shepherd-task-create-ignorance-reduction-plan` to the skills list in all four scripts:
+
+- install-task-shepherd.ps1 — will copy the skill on install (skips if already present)
+- install-task-shepherd.sh — same behavior, bash version
+- uninstall-task-shepherd.ps1 — will remove the skill on uninstall
+- uninstall-task-shepherd.sh — same behavior, bash version
+
+I also noticed `shepherd-task-create-post-mortem` exists in the repo's `skills/` directory but isn't in these scripts — let me know if you'd like that added too.
+
+
+### 19:41 Prompt
+
+Oh yes. I do need that also.