Prompt to create skill to create issues

Author: edburns

1917-java-embed-rust-cli-runtime-remove-before-merge/20260728-dd-3039145-create-skill-to-create-issues.md

@@ -0,0 +1,162 @@
+## dd-3039145-cast-phase-4-into-issues
+
+### Gather previous issue casting actions
+
+Examine the following skills.
+
+C:\Users\edburns\.copilot\skills\shepherd-task-from-assignment-to-ready
+C:\Users\edburns\.copilot\skills\shepherd-task-from-ready-to-merged-to-base
+C:\Users\edburns\.copilot\skills\shepherd-task-approve-workflows-and-wait-for-completion
+C:\Users\edburns\.copilot\skills\shepherd-task-create-ignorance-reduction-plan
+C:\Users\edburns\.copilot\skills\shepherd-task-create-post-mortem
+
+and the scripts in this directory
+
+C:\Users\edburns\.copilot\plugins\shepherd-task
+
+Taken together, these scripts constitute the "shepherd-task" system.
+
+Read the `C:\Users\edburns\.copilot\plugins\shepherd-task\README.md` to understand how the "shepherd-task" system works.
+
+In this session we are building a skill that simplifies the satisfaction of this precondation in the README.
+
+> 1. The specification for the job to be done is encoded in an ordered set of GitHub issues in the issue tracker of the GitHub repository.
+
+This new skill will be called `shepherd-task-create-issues-from-plan`.
+
+The following four H4 sections are previous iterations where I directed the performing of actions to create the issues as child issues of a pre-existing parent issue. First, we must discern the common inputs for the `shepherd-task-create-issues-from-plan` skill. I expect we will need at least the following. You will likely find more.
+
+1. The name of the base branch on which the agent must perform the work.
+1. The repo in which to perfom the work.
+1. The number of the pre-existing parent issue in which the skill will create the child issues.
+1. The repo-relative path to the ignorance reduction plan document.
+1. Completely unambiguous references to the following sections within the ignorance reduction plan document
+   a. The "questions to answer before writing code" section.
+   b. The "Implementation (the build order)" section.
+1. A reference to one or more example issues to give the agent concrete examples of style and format for creating issues.
+   
+Review the following four H4 sections, along with the preceding list, and derive the common list of inputs. State the derived list.
+
+#### 01 1682-java-tool-ergonomics-prompts-remove-before-merge
+
+Read `copilot-sdk/1682-java-tool-ergonomics-prompts-remove-before-merge/dd-3018003-ignorance-reduction-for-implementation-plan.md` (the plan) to get the context. 
+
+✅✅Pay very close attention to each **Resolution:** to the questions in `Phase 3 — Ignorance reduction: questions to answer before writing code`.
+
+In this session, we are creating issues of type **Task** as children of Epic https://github.com/github/copilot-sdk/issues/1682 . These issues correspond to the sub-sections in `## Phase 4 — Implementation (the build order)`.
+
+I want you to use `gh` to create issues as sub-issues of 1682.
+
+- I will dispatch these issues by assigning them to an agent. Leave them unassigned for now.
+
+- The description you put in the issues you create is the specification for the work the agent assigned to the issue must do. Therefore, you need to be very specific and targeted when writing the description.
+
+- Set the type to **Task**.
+
+- Each issue will be worked on and resolved in serial. You can assume:
+
+   - All issues will operate in this topic branch of `upstream`: `edburns/1682-java-tool-ergonomics`. 
+
+   - The assignee agent has access to the topic branch and, most importantly, to the prompts in the directory `1682-java-tool-ergonomics-prompts-remove-before-merge`, which includes the plan. Therefore, you can instruct the agent to access the plan by reference, you don't need to reference it by value directly in the issue.
+   
+- The sub-sections of `## Phase 4 — Implementation (the build order)` have essential details for each corresponding **Task**.
+
+- Instruct the agent to read the entire plan before working.
+
+- Instruct the agent to carefully re-read the relevant sections of the of the plan. ❌❌You can't just say, "read the relevant sections of the plan". ✅✅In the description of the issue, list exactly what sections of the plan apply to this particular issue.
+   
+- Though the sub-sections of `## Phase 4 — Implementation (the build order)` have essential details for each corresponding **Task**, I want you to carefully consider if there additional gating tests you can add so that as the agent proceeds from one task to the next, the likelihood of rework is reduced.
+
+
+
+#### 02 1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge
+
+Carefully read the plan `copilot-sdk/1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md`.
+
+We have completed Phases 1 - 3. We are now on Phase 4.
+
+For each sub item in Phase 4, file a child issue of Feature #1810.
+
+Use `gh` to look at Epic #1682 and its child issues for the standard of verbosity and concreteness for issue descriptions.
+
+The issue should be assignable to a coding agent and there must be sufficient detail in the description for the agent to proceed to completion.
+
+Pull out the specific relevant content from Phase 3 as it applies to this current issue in Phase 4. 
+
+Tell the agent to take `edburns/1810-java-tool-ergonomics-tool-as-lambda` as the base branch. When I assign the issue to the coding agent, I will set this as the base branch.
+
+Tell the agent to read `1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md`, which is present on the branch, for context.
+
+Tell the agent which sub-item within Phase 4 they are solving.
+
+Tell the agent that each issue will be assigned, resolved and merged to the base branch in the order in which they appear in the plan.
+
+Tell the agent to update the check boxes in their phase in `1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md` as they complete their work.
+
+No work is to start until I assign each issue to the coding agent, in turn.
+
+Once you have filed all the issues, update `1810-java-tool-ergonomics-tool-as-lambda-remove-before-merge/1810-ignorance-reduction-for-implementation-plan.md` Phase 4 with progress checkboxes the agents can check off as they work.
+
+
+
+#### 03 dd-3017826-java-real-estate-demo-remove-before-merge
+
+Read `dd-3017826-java-real-estate-demo-remove-before-merge\dd-3017826-java-real-estate-demo-ignorance-reduction-plan.md` (the plan) to get the context. 
+
+✅✅Pay very close attention to each **Resolution:** to the questions in `Phase 2 — Ignorance reduction: questions to answer before writing code`.
+
+In this session, we are creating sub-issues as children of https://github.com/edburns/Build26-BRK206-your-agent-anywhere-multiclient-multidevice-with-github-copilot-sdk/issues/2 . These issues correspond to the sub-sections in `## Phase 3 — Implementation (build order)`.
+
+I want you to use `gh` to create issues as sub-issues of #2.
+
+- I will dispatch these issues by assigning them to an agent. Leave them unassigned for now.
+
+- The description you put in the issues you create is the specification for the work the agent assigned to the issue must do. Therefore, you need to be very specific and targeted when writing the description.
+
+- Each issue will be worked on and resolved in serial. You can assume:
+
+   - All issues will operate in this topic branch of `origin`: `edburns/2-build-out-demo`. 
+
+   - The assignee agent has access to the topic branch and, most importantly, to the prompts in the directory `dd-3017826-java-real-estate-demo-remove-before-merge`, which includes the plan. Therefore, you can instruct the agent to access the plan by reference, you don't need to reference it by value directly in the issue.
+   
+- The sub-sections of `## Phase 3 — Implementation (build order)` have essential details for each corresponding sub-issue.
+
+- Instruct the agent to read the entire plan before working.
+
+- Instruct the agent to carefully re-read the relevant sections of the of the plan. ❌❌You can't just say, "read the relevant sections of the plan". ✅✅In the description of the issue, list exactly what sections of the plan apply to this particular issue.
+   
+- Though the sub-sections of `## Phase 3 — Implementation (build order)` have essential details for each corresponding sub-issue, I want you to carefully consider if there additional gating tests you can add so that as the agent proceeds from one task to the next, the likelihood of rework is reduced.
+
+
+#### 04 28-python-agent-demo-remove-before-merge
+
+Read `28-python-agent-demo-remove-before-merge/28-python-agent-demo-ignorance-reduction-plan.md` (the plan) to get the context. 
+
+✅✅Pay very close attention to each **Resolution:** to the questions in `Phase 2 — Ignorance reduction: questions to answer before writing code`. These pertain to the implementation tasks in Phase 3. ✅✅✅ Make sure to put into the description explicit instructions on how to access the relevant spike research. 
+
+In this session, we are creating sub-issues as children of https://github.com/edburns/Build26-BRK206-your-agent-anywhere-multiclient-multidevice-with-github-copilot-sdk/issues/28 . These issues correspond to the sub-sections in `## Phase 3 — Implementation (build order)`.
+
+I want you to use `gh` to create issues as sub-issues of #28
+
+- I will dispatch these issues by assigning them to an agent. Leave them unassigned for now.
+
+- The description you put in the issues you create is the specification for the work the agent assigned to the issue must do. Therefore, you need to be very specific and targeted when writing the description.
+
+- Again, ✅✅For each **Resolution:** to the questions in `Phase 2 — Ignorance reduction: questions to answer before writing code`, include the relevant Resolution values in the issue description. These pertain to the implementation tasks in Phase 3. ✅✅✅ Make sure to put into the description explicit instructions on how to access the relevant spike research for that task.
+
+- For tasks dealing with the UI, make sure to refer to the relevant screengrabs, but only ones within `28-python-agent-demo-remove-before-merge/`.
+
+- Each issue will be worked on and resolved in serial. You can assume:
+
+   - All issues will operate in this topic branch of `origin`: `edburns/28-python-agent-demo`. 
+
+   - The assignee agent has access to the topic branch and, most importantly, to the prompts in the directory `28-python-agent-demo-remove-before-merge/`, which includes the plan. Therefore, you can instruct the agent to access the plan by reference, you don't need to reference it by value directly in the issue.
+   
+- The sub-sections of `## Phase 3 — Implementation (build order)` have essential details for each corresponding sub-issue.
+
+- Instruct the agent to read the entire plan before working.
+
+- Instruct the agent to carefully re-read the relevant sections of the of the plan. ❌❌You can't just say, "read the relevant sections of the plan". ✅✅In the description of the issue, list exactly what sections of the plan apply to this particular issue.
+   
+- Though the sub-sections of `## Phase 3 — Implementation (build order)` have essential details for each corresponding sub-issue, I want you to carefully consider if there additional gating tests you can add so that as the agent proceeds from one task to the next, the likelihood of rework is reduced.
+