diff --git a/instructions/r3/core/skills/research/README.md b/instructions/r3/core/skills/research/README.md index a49556bfc..5e9af8f6b 100644 --- a/instructions/r3/core/skills/research/README.md +++ b/instructions/r3/core/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`workflows/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `workflows/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `workflows/self-help-flow.md` (as a cautionary example). diff --git a/instructions/r3/core/skills/research/SKILL.md b/instructions/r3/core/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/instructions/r3/core/skills/research/SKILL.md +++ b/instructions/r3/core/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/instructions/r3/core/workflows/coding-agents-prompting-flow.md b/instructions/r3/core/workflows/coding-agents-prompting-flow.md index 0dbcbd0b3..dd77cb346 100644 --- a/instructions/r3/core/workflows/coding-agents-prompting-flow.md +++ b/instructions/r3/core/workflows/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/instructions/r3/core/workflows/modernization-flow-analysis.md b/instructions/r3/core/workflows/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/instructions/r3/core/workflows/modernization-flow-analysis.md +++ b/instructions/r3/core/workflows/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/instructions/r3/core/workflows/modernization-flow-implement.md b/instructions/r3/core/workflows/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/instructions/r3/core/workflows/modernization-flow-implement.md +++ b/instructions/r3/core/workflows/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/instructions/r3/core/workflows/modernization-flow-mapping.md b/instructions/r3/core/workflows/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/instructions/r3/core/workflows/modernization-flow-mapping.md +++ b/instructions/r3/core/workflows/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/instructions/r3/core/workflows/modernization-flow.md b/instructions/r3/core/workflows/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/instructions/r3/core/workflows/modernization-flow.md +++ b/instructions/r3/core/workflows/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-antigravity-light/skills/coding-agents-prompting-flow/SKILL.md b/plugins/core-antigravity-light/skills/coding-agents-prompting-flow/SKILL.md index bb878cfdd..d9ea16717 100644 --- a/plugins/core-antigravity-light/skills/coding-agents-prompting-flow/SKILL.md +++ b/plugins/core-antigravity-light/skills/coding-agents-prompting-flow/SKILL.md @@ -24,7 +24,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -86,7 +86,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-antigravity-light/skills/modernization-flow/SKILL.md b/plugins/core-antigravity-light/skills/modernization-flow/SKILL.md index d9fe500f2..c20e2c6c4 100644 --- a/plugins/core-antigravity-light/skills/modernization-flow/SKILL.md +++ b/plugins/core-antigravity-light/skills/modernization-flow/SKILL.md @@ -28,7 +28,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-analysis.md b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-analysis.md index 2b64084b0..6f1dd855b 100644 --- a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-analysis.md +++ b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-analysis.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -17,7 +17,7 @@ ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-implement.md b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-implement.md index 5a411eaab..d525ae744 100644 --- a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-implement.md +++ b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-implement.md @@ -3,7 +3,7 @@ ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-mapping.md b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-mapping.md index b3271bd9d..aa7f728ad 100644 --- a/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-mapping.md +++ b/plugins/core-antigravity-light/skills/modernization-flow/phases/modernization-flow-mapping.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -15,7 +15,7 @@ ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -44,7 +44,7 @@ ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-antigravity-light/skills/research/README.md b/plugins/core-antigravity-light/skills/research/README.md index 9fb675c60..2dac9d281 100644 --- a/plugins/core-antigravity-light/skills/research/README.md +++ b/plugins/core-antigravity-light/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`skills/research-flow/SKILL.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `skills/research-flow/SKILL.md`, `skills/orchestration/assets/o-team-manager.md`, and `skills/self-help-flow/SKILL.md` (as a cautionary example). diff --git a/plugins/core-antigravity-light/skills/research/SKILL.md b/plugins/core-antigravity-light/skills/research/SKILL.md index f5d079939..ad2d88979 100644 --- a/plugins/core-antigravity-light/skills/research/SKILL.md +++ b/plugins/core-antigravity-light/skills/research/SKILL.md @@ -47,7 +47,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-antigravity/skills/coding-agents-prompting-flow/SKILL.md b/plugins/core-antigravity/skills/coding-agents-prompting-flow/SKILL.md index bb878cfdd..d9ea16717 100644 --- a/plugins/core-antigravity/skills/coding-agents-prompting-flow/SKILL.md +++ b/plugins/core-antigravity/skills/coding-agents-prompting-flow/SKILL.md @@ -24,7 +24,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -86,7 +86,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-antigravity/skills/modernization-flow/SKILL.md b/plugins/core-antigravity/skills/modernization-flow/SKILL.md index d9fe500f2..c20e2c6c4 100644 --- a/plugins/core-antigravity/skills/modernization-flow/SKILL.md +++ b/plugins/core-antigravity/skills/modernization-flow/SKILL.md @@ -28,7 +28,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-analysis.md b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-analysis.md index 2b64084b0..6f1dd855b 100644 --- a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-analysis.md +++ b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-analysis.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -17,7 +17,7 @@ ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-implement.md b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-implement.md index 5a411eaab..d525ae744 100644 --- a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-implement.md +++ b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-implement.md @@ -3,7 +3,7 @@ ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-mapping.md b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-mapping.md index b3271bd9d..aa7f728ad 100644 --- a/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-mapping.md +++ b/plugins/core-antigravity/skills/modernization-flow/phases/modernization-flow-mapping.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -15,7 +15,7 @@ ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -44,7 +44,7 @@ ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-antigravity/skills/research/README.md b/plugins/core-antigravity/skills/research/README.md index 9fb675c60..2dac9d281 100644 --- a/plugins/core-antigravity/skills/research/README.md +++ b/plugins/core-antigravity/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`skills/research-flow/SKILL.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `skills/research-flow/SKILL.md`, `skills/orchestration/assets/o-team-manager.md`, and `skills/self-help-flow/SKILL.md` (as a cautionary example). diff --git a/plugins/core-antigravity/skills/research/SKILL.md b/plugins/core-antigravity/skills/research/SKILL.md index f5d079939..ad2d88979 100644 --- a/plugins/core-antigravity/skills/research/SKILL.md +++ b/plugins/core-antigravity/skills/research/SKILL.md @@ -47,7 +47,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-claude-light/skills/research/README.md b/plugins/core-claude-light/skills/research/README.md index a49556bfc..5e9af8f6b 100644 --- a/plugins/core-claude-light/skills/research/README.md +++ b/plugins/core-claude-light/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`workflows/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `workflows/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `workflows/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-claude-light/skills/research/SKILL.md b/plugins/core-claude-light/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-claude-light/skills/research/SKILL.md +++ b/plugins/core-claude-light/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-claude-light/workflows/coding-agents-prompting-flow.md b/plugins/core-claude-light/workflows/coding-agents-prompting-flow.md index 556cc1aa8..c54d5c5fd 100644 --- a/plugins/core-claude-light/workflows/coding-agents-prompting-flow.md +++ b/plugins/core-claude-light/workflows/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-claude-light/workflows/modernization-flow-analysis.md b/plugins/core-claude-light/workflows/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-claude-light/workflows/modernization-flow-analysis.md +++ b/plugins/core-claude-light/workflows/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-claude-light/workflows/modernization-flow-implement.md b/plugins/core-claude-light/workflows/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-claude-light/workflows/modernization-flow-implement.md +++ b/plugins/core-claude-light/workflows/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-claude-light/workflows/modernization-flow-mapping.md b/plugins/core-claude-light/workflows/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-claude-light/workflows/modernization-flow-mapping.md +++ b/plugins/core-claude-light/workflows/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-claude-light/workflows/modernization-flow.md b/plugins/core-claude-light/workflows/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-claude-light/workflows/modernization-flow.md +++ b/plugins/core-claude-light/workflows/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-claude/skills/research/README.md b/plugins/core-claude/skills/research/README.md index a49556bfc..5e9af8f6b 100644 --- a/plugins/core-claude/skills/research/README.md +++ b/plugins/core-claude/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`workflows/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `workflows/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `workflows/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `workflows/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `workflows/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-claude/skills/research/SKILL.md b/plugins/core-claude/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-claude/skills/research/SKILL.md +++ b/plugins/core-claude/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-claude/workflows/coding-agents-prompting-flow.md b/plugins/core-claude/workflows/coding-agents-prompting-flow.md index 556cc1aa8..c54d5c5fd 100644 --- a/plugins/core-claude/workflows/coding-agents-prompting-flow.md +++ b/plugins/core-claude/workflows/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-claude/workflows/modernization-flow-analysis.md b/plugins/core-claude/workflows/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-claude/workflows/modernization-flow-analysis.md +++ b/plugins/core-claude/workflows/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-claude/workflows/modernization-flow-implement.md b/plugins/core-claude/workflows/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-claude/workflows/modernization-flow-implement.md +++ b/plugins/core-claude/workflows/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-claude/workflows/modernization-flow-mapping.md b/plugins/core-claude/workflows/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-claude/workflows/modernization-flow-mapping.md +++ b/plugins/core-claude/workflows/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-claude/workflows/modernization-flow.md b/plugins/core-claude/workflows/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-claude/workflows/modernization-flow.md +++ b/plugins/core-claude/workflows/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-codex-light/.agents/skills/coding-agents-prompting-flow/SKILL.md b/plugins/core-codex-light/.agents/skills/coding-agents-prompting-flow/SKILL.md index 664732765..0ba957a23 100644 --- a/plugins/core-codex-light/.agents/skills/coding-agents-prompting-flow/SKILL.md +++ b/plugins/core-codex-light/.agents/skills/coding-agents-prompting-flow/SKILL.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-codex-light/.agents/skills/modernization-flow/SKILL.md b/plugins/core-codex-light/.agents/skills/modernization-flow/SKILL.md index 74319010a..498f7079d 100644 --- a/plugins/core-codex-light/.agents/skills/modernization-flow/SKILL.md +++ b/plugins/core-codex-light/.agents/skills/modernization-flow/SKILL.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md index 2b64084b0..6f1dd855b 100644 --- a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md +++ b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -17,7 +17,7 @@ ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-implement.md b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-implement.md index 5a411eaab..d525ae744 100644 --- a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-implement.md +++ b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-implement.md @@ -3,7 +3,7 @@ ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md index b3271bd9d..aa7f728ad 100644 --- a/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md +++ b/plugins/core-codex-light/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -15,7 +15,7 @@ ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -44,7 +44,7 @@ ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-codex-light/.agents/skills/research/README.md b/plugins/core-codex-light/.agents/skills/research/README.md index 9fb675c60..2dac9d281 100644 --- a/plugins/core-codex-light/.agents/skills/research/README.md +++ b/plugins/core-codex-light/.agents/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`skills/research-flow/SKILL.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `skills/research-flow/SKILL.md`, `skills/orchestration/assets/o-team-manager.md`, and `skills/self-help-flow/SKILL.md` (as a cautionary example). diff --git a/plugins/core-codex-light/.agents/skills/research/SKILL.md b/plugins/core-codex-light/.agents/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-codex-light/.agents/skills/research/SKILL.md +++ b/plugins/core-codex-light/.agents/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-codex/.agents/skills/coding-agents-prompting-flow/SKILL.md b/plugins/core-codex/.agents/skills/coding-agents-prompting-flow/SKILL.md index 664732765..0ba957a23 100644 --- a/plugins/core-codex/.agents/skills/coding-agents-prompting-flow/SKILL.md +++ b/plugins/core-codex/.agents/skills/coding-agents-prompting-flow/SKILL.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-codex/.agents/skills/modernization-flow/SKILL.md b/plugins/core-codex/.agents/skills/modernization-flow/SKILL.md index 74319010a..498f7079d 100644 --- a/plugins/core-codex/.agents/skills/modernization-flow/SKILL.md +++ b/plugins/core-codex/.agents/skills/modernization-flow/SKILL.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md index 2b64084b0..6f1dd855b 100644 --- a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md +++ b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-analysis.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -17,7 +17,7 @@ ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-implement.md b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-implement.md index 5a411eaab..d525ae744 100644 --- a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-implement.md +++ b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-implement.md @@ -3,7 +3,7 @@ ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md index b3271bd9d..aa7f728ad 100644 --- a/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md +++ b/plugins/core-codex/.agents/skills/modernization-flow/phases/modernization-flow-mapping.md @@ -3,7 +3,7 @@ ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -15,7 +15,7 @@ ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -44,7 +44,7 @@ ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-codex/.agents/skills/research/README.md b/plugins/core-codex/.agents/skills/research/README.md index 9fb675c60..2dac9d281 100644 --- a/plugins/core-codex/.agents/skills/research/README.md +++ b/plugins/core-codex/.agents/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`skills/research-flow/SKILL.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `skills/research-flow/SKILL.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `skills/self-help-flow/SKILL.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `skills/research-flow/SKILL.md`, `skills/orchestration/assets/o-team-manager.md`, and `skills/self-help-flow/SKILL.md` (as a cautionary example). diff --git a/plugins/core-codex/.agents/skills/research/SKILL.md b/plugins/core-codex/.agents/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-codex/.agents/skills/research/SKILL.md +++ b/plugins/core-codex/.agents/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-copilot-light/commands/coding-agents-prompting-flow.md b/plugins/core-copilot-light/commands/coding-agents-prompting-flow.md index 2900faac7..03f937315 100644 --- a/plugins/core-copilot-light/commands/coding-agents-prompting-flow.md +++ b/plugins/core-copilot-light/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-copilot-light/commands/modernization-flow-analysis.md b/plugins/core-copilot-light/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-copilot-light/commands/modernization-flow-analysis.md +++ b/plugins/core-copilot-light/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-copilot-light/commands/modernization-flow-implement.md b/plugins/core-copilot-light/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-copilot-light/commands/modernization-flow-implement.md +++ b/plugins/core-copilot-light/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-copilot-light/commands/modernization-flow-mapping.md b/plugins/core-copilot-light/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-copilot-light/commands/modernization-flow-mapping.md +++ b/plugins/core-copilot-light/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-copilot-light/commands/modernization-flow.md b/plugins/core-copilot-light/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-copilot-light/commands/modernization-flow.md +++ b/plugins/core-copilot-light/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-copilot-light/skills/research/README.md b/plugins/core-copilot-light/skills/research/README.md index 2bc716ee7..94d8c0bbe 100644 --- a/plugins/core-copilot-light/skills/research/README.md +++ b/plugins/core-copilot-light/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.agent.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.agent.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-copilot-light/skills/research/SKILL.md b/plugins/core-copilot-light/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-copilot-light/skills/research/SKILL.md +++ b/plugins/core-copilot-light/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-copilot-standalone-light/.github/prompts/coding-agents-prompting-flow.prompt.md b/plugins/core-copilot-standalone-light/.github/prompts/coding-agents-prompting-flow.prompt.md index 2900faac7..03f937315 100644 --- a/plugins/core-copilot-standalone-light/.github/prompts/coding-agents-prompting-flow.prompt.md +++ b/plugins/core-copilot-standalone-light/.github/prompts/coding-agents-prompting-flow.prompt.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-analysis.prompt.md b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-analysis.prompt.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-analysis.prompt.md +++ b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-analysis.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-implement.prompt.md b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-implement.prompt.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-implement.prompt.md +++ b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-implement.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-mapping.prompt.md b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-mapping.prompt.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-mapping.prompt.md +++ b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow-mapping.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow.prompt.md b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow.prompt.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow.prompt.md +++ b/plugins/core-copilot-standalone-light/.github/prompts/modernization-flow.prompt.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-copilot-standalone-light/.github/skills/research/README.md b/plugins/core-copilot-standalone-light/.github/skills/research/README.md index 5972aa05f..f799337ca 100644 --- a/plugins/core-copilot-standalone-light/.github/skills/research/README.md +++ b/plugins/core-copilot-standalone-light/.github/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.agent.md`) is the skill-level tracker; `research-flow-state.md` (`prompts/research-flow.prompt.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `prompts/research-flow.prompt.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `prompts/self-help-flow.prompt.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `prompts/research-flow.prompt.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `prompts/self-help-flow.prompt.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.agent.md`, `prompts/research-flow.prompt.md`, `skills/orchestration/assets/o-team-manager.md`, and `prompts/self-help-flow.prompt.md` (as a cautionary example). diff --git a/plugins/core-copilot-standalone-light/.github/skills/research/SKILL.md b/plugins/core-copilot-standalone-light/.github/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-copilot-standalone-light/.github/skills/research/SKILL.md +++ b/plugins/core-copilot-standalone-light/.github/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-copilot-standalone/.github/prompts/coding-agents-prompting-flow.prompt.md b/plugins/core-copilot-standalone/.github/prompts/coding-agents-prompting-flow.prompt.md index 2900faac7..03f937315 100644 --- a/plugins/core-copilot-standalone/.github/prompts/coding-agents-prompting-flow.prompt.md +++ b/plugins/core-copilot-standalone/.github/prompts/coding-agents-prompting-flow.prompt.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-analysis.prompt.md b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-analysis.prompt.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-analysis.prompt.md +++ b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-analysis.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-implement.prompt.md b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-implement.prompt.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-implement.prompt.md +++ b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-implement.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-mapping.prompt.md b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-mapping.prompt.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-copilot-standalone/.github/prompts/modernization-flow-mapping.prompt.md +++ b/plugins/core-copilot-standalone/.github/prompts/modernization-flow-mapping.prompt.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-copilot-standalone/.github/prompts/modernization-flow.prompt.md b/plugins/core-copilot-standalone/.github/prompts/modernization-flow.prompt.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-copilot-standalone/.github/prompts/modernization-flow.prompt.md +++ b/plugins/core-copilot-standalone/.github/prompts/modernization-flow.prompt.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-copilot-standalone/.github/skills/research/README.md b/plugins/core-copilot-standalone/.github/skills/research/README.md index 5972aa05f..f799337ca 100644 --- a/plugins/core-copilot-standalone/.github/skills/research/README.md +++ b/plugins/core-copilot-standalone/.github/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.agent.md`) is the skill-level tracker; `research-flow-state.md` (`prompts/research-flow.prompt.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `prompts/research-flow.prompt.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `prompts/self-help-flow.prompt.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `prompts/research-flow.prompt.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `prompts/self-help-flow.prompt.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.agent.md`, `prompts/research-flow.prompt.md`, `skills/orchestration/assets/o-team-manager.md`, and `prompts/self-help-flow.prompt.md` (as a cautionary example). diff --git a/plugins/core-copilot-standalone/.github/skills/research/SKILL.md b/plugins/core-copilot-standalone/.github/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-copilot-standalone/.github/skills/research/SKILL.md +++ b/plugins/core-copilot-standalone/.github/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-copilot/commands/coding-agents-prompting-flow.md b/plugins/core-copilot/commands/coding-agents-prompting-flow.md index 2900faac7..03f937315 100644 --- a/plugins/core-copilot/commands/coding-agents-prompting-flow.md +++ b/plugins/core-copilot/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-copilot/commands/modernization-flow-analysis.md b/plugins/core-copilot/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-copilot/commands/modernization-flow-analysis.md +++ b/plugins/core-copilot/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-copilot/commands/modernization-flow-implement.md b/plugins/core-copilot/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-copilot/commands/modernization-flow-implement.md +++ b/plugins/core-copilot/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-copilot/commands/modernization-flow-mapping.md b/plugins/core-copilot/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-copilot/commands/modernization-flow-mapping.md +++ b/plugins/core-copilot/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-copilot/commands/modernization-flow.md b/plugins/core-copilot/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-copilot/commands/modernization-flow.md +++ b/plugins/core-copilot/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-copilot/skills/research/README.md b/plugins/core-copilot/skills/research/README.md index 2bc716ee7..94d8c0bbe 100644 --- a/plugins/core-copilot/skills/research/README.md +++ b/plugins/core-copilot/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.agent.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.agent.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.agent.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-copilot/skills/research/SKILL.md b/plugins/core-copilot/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-copilot/skills/research/SKILL.md +++ b/plugins/core-copilot/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-cursor-light/commands/coding-agents-prompting-flow.md b/plugins/core-cursor-light/commands/coding-agents-prompting-flow.md index 5992b1ed3..21418c4af 100644 --- a/plugins/core-cursor-light/commands/coding-agents-prompting-flow.md +++ b/plugins/core-cursor-light/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-cursor-light/commands/modernization-flow-analysis.md b/plugins/core-cursor-light/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-cursor-light/commands/modernization-flow-analysis.md +++ b/plugins/core-cursor-light/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-cursor-light/commands/modernization-flow-implement.md b/plugins/core-cursor-light/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-cursor-light/commands/modernization-flow-implement.md +++ b/plugins/core-cursor-light/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-cursor-light/commands/modernization-flow-mapping.md b/plugins/core-cursor-light/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-cursor-light/commands/modernization-flow-mapping.md +++ b/plugins/core-cursor-light/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-cursor-light/commands/modernization-flow.md b/plugins/core-cursor-light/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-cursor-light/commands/modernization-flow.md +++ b/plugins/core-cursor-light/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-cursor-light/skills/research/README.md b/plugins/core-cursor-light/skills/research/README.md index a8e900058..b90da6f5e 100644 --- a/plugins/core-cursor-light/skills/research/README.md +++ b/plugins/core-cursor-light/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-cursor-light/skills/research/SKILL.md b/plugins/core-cursor-light/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-cursor-light/skills/research/SKILL.md +++ b/plugins/core-cursor-light/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-cursor-standalone-light/.cursor/commands/coding-agents-prompting-flow.md b/plugins/core-cursor-standalone-light/.cursor/commands/coding-agents-prompting-flow.md index 5992b1ed3..21418c4af 100644 --- a/plugins/core-cursor-standalone-light/.cursor/commands/coding-agents-prompting-flow.md +++ b/plugins/core-cursor-standalone-light/.cursor/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-analysis.md b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-analysis.md +++ b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-implement.md b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-implement.md +++ b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-mapping.md b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-mapping.md +++ b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow.md b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow.md +++ b/plugins/core-cursor-standalone-light/.cursor/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-cursor-standalone-light/.cursor/skills/research/README.md b/plugins/core-cursor-standalone-light/.cursor/skills/research/README.md index a8e900058..b90da6f5e 100644 --- a/plugins/core-cursor-standalone-light/.cursor/skills/research/README.md +++ b/plugins/core-cursor-standalone-light/.cursor/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-cursor-standalone-light/.cursor/skills/research/SKILL.md b/plugins/core-cursor-standalone-light/.cursor/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-cursor-standalone-light/.cursor/skills/research/SKILL.md +++ b/plugins/core-cursor-standalone-light/.cursor/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-cursor-standalone/.cursor/commands/coding-agents-prompting-flow.md b/plugins/core-cursor-standalone/.cursor/commands/coding-agents-prompting-flow.md index 5992b1ed3..21418c4af 100644 --- a/plugins/core-cursor-standalone/.cursor/commands/coding-agents-prompting-flow.md +++ b/plugins/core-cursor-standalone/.cursor/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-analysis.md b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-analysis.md +++ b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-implement.md b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-implement.md +++ b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-mapping.md b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-mapping.md +++ b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow.md b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-cursor-standalone/.cursor/commands/modernization-flow.md +++ b/plugins/core-cursor-standalone/.cursor/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-cursor-standalone/.cursor/skills/research/README.md b/plugins/core-cursor-standalone/.cursor/skills/research/README.md index a8e900058..b90da6f5e 100644 --- a/plugins/core-cursor-standalone/.cursor/skills/research/README.md +++ b/plugins/core-cursor-standalone/.cursor/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-cursor-standalone/.cursor/skills/research/SKILL.md b/plugins/core-cursor-standalone/.cursor/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-cursor-standalone/.cursor/skills/research/SKILL.md +++ b/plugins/core-cursor-standalone/.cursor/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way) diff --git a/plugins/core-cursor/commands/coding-agents-prompting-flow.md b/plugins/core-cursor/commands/coding-agents-prompting-flow.md index 5992b1ed3..21418c4af 100644 --- a/plugins/core-cursor/commands/coding-agents-prompting-flow.md +++ b/plugins/core-cursor/commands/coding-agents-prompting-flow.md @@ -26,7 +26,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 5. Orchestrator and subagents MUST USE SKILL `coding-agents-prompt-authoring`. 6. No rush, take your time, MUST FOLLOW WORKFLOW ENTIRELY, no skipping. 7. This workflow MUST be used with Fable, Opus, GPT-6.1-Sol+ class models => IF NOT - DEMAND USER TO SWITCH MODEL. -8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state` file. +8. Workflow state MUST be saved to `agents/TEMP//coding-agents-prompting-flow-state.md` file. @@ -88,7 +88,7 @@ Orchestrates prompt authoring/adaptation via `discover -> extract+intake -> blue 1. Validate final artifacts against intent, contracts, failure modes, and traceability. -2. Input: `Prompt Brief` + `Blueprint` + `Candidate Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). +2. Input: `Prompt Brief` + `Blueprint` + `Prompt Set` + `Simulation Notes`. Output: `Final Prompt Set` + `Validation Pack` (`Checklist Results`, `Tests`, `Failure Modes`, `Traceability`; persistent report optional in FEATURE PLAN folder as validation-report.md). 3. Update `coding-agents-prompting-flow-state.md` and mark complete. 4. HITL final approval required before persistence; small tasks may stay in-memory and be returned in message. diff --git a/plugins/core-cursor/commands/modernization-flow-analysis.md b/plugins/core-cursor/commands/modernization-flow-analysis.md index 3e1710fd4..d142a80bc 100644 --- a/plugins/core-cursor/commands/modernization-flow-analysis.md +++ b/plugins/core-cursor/commands/modernization-flow-analysis.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 2: Old Code Analysis** -1. Complete Phase 1 first +1. Complete Phase 1 first, unless on the reduced route recorded in the state file 2. Process each project separately 3. Analyze code and tests 4. Create original-code-specs files @@ -26,7 +26,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 1 (all reference code specs created) +**PREREQUISITES:** Complete Phase 1 (all reference code specs created), unless on the reduced route recorded in the state file **OBJECTIVES:** - Create complete, factual specification of existing code diff --git a/plugins/core-cursor/commands/modernization-flow-implement.md b/plugins/core-cursor/commands/modernization-flow-implement.md index e6cb3281e..2c6391d04 100644 --- a/plugins/core-cursor/commands/modernization-flow-implement.md +++ b/plugins/core-cursor/commands/modernization-flow-implement.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Context **PREREQUISITES:** -- Complete Phase 7 (final cross-project review) +- Complete Phase 7 (final cross-project review), unless on the reduced route recorded in the state file - **EXPLICIT HUMAN APPROVAL** of all target specs ## Requirements diff --git a/plugins/core-cursor/commands/modernization-flow-mapping.md b/plugins/core-cursor/commands/modernization-flow-mapping.md index e1e92cc65..43b7bd1a4 100644 --- a/plugins/core-cursor/commands/modernization-flow-mapping.md +++ b/plugins/core-cursor/commands/modernization-flow-mapping.md @@ -12,7 +12,7 @@ baseSchema: docs/schemas/phase.md ## Phase Flow **Phase 6: Implementation Mapping** -1. Complete Phase 5 first +1. Complete Phase 5 first, unless on the reduced route recorded in the state file 2. Define technical approaches 3. Compare multiple alternatives 4. Map source to target @@ -24,7 +24,7 @@ baseSchema: docs/schemas/phase.md ## Context -**PREREQUISITES:** Complete Phase 5 (cross-project analysis) +**PREREQUISITES:** Complete Phase 5 (cross-project analysis), unless on the reduced route recorded in the state file **OBJECTIVES:** - Define technical approaches for modernization @@ -53,7 +53,7 @@ baseSchema: docs/schemas/phase.md ## Requirements - **MUST** process each project separately -- **MUST** re-read `docs/cross-project-analysis.md` +- **MUST** re-read `docs/cross-project-analysis.md` if it exists - **MUST** re-read matching `docs/original-code-specs-.md` - **MUST** re-read both incoming/outgoing dependency if those exist `docs/target-code-specs-.md` - **MUST** create `docs/target-code-specs-.md` for each project diff --git a/plugins/core-cursor/commands/modernization-flow.md b/plugins/core-cursor/commands/modernization-flow.md index 4a9edaa8b..95dcd72a2 100644 --- a/plugins/core-cursor/commands/modernization-flow.md +++ b/plugins/core-cursor/commands/modernization-flow.md @@ -30,7 +30,7 @@ This modernization process is designed to systematically analyze, specify, and i - If user did not specify any preferences perform all steps except optional. - User CAN customize and ask only for specific steps OR steps could have been done already OR towards specific goal OR for specific case, in this case LISTEN and ADOPT to the user. -- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, unless you discover dependencies and project becomes bigger. +- Modernization scope could be small or could be done in place (example: upgrade Java 8 to 17 or 17 to 21), in this case only use `Phase 2` and `Phase 6`, skip the other phases and their prerequisites, record this in the state file, unless you discover dependencies and project becomes bigger. - If there is no need to rewrite code (example: upgrade .NET 6 to .NET 8), then take original and target code specs LIGHTLY, only document WHAT IS NECESSARY TO CHANGE (example: new way to use app builder). ## Modernization Flow - Phase Overview diff --git a/plugins/core-cursor/skills/research/README.md b/plugins/core-cursor/skills/research/README.md index a8e900058..b90da6f5e 100644 --- a/plugins/core-cursor/skills/research/README.md +++ b/plugins/core-cursor/skills/research/README.md @@ -17,7 +17,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - "MUST NOT update CONTEXT.md, ARCHITECTURE.md, IMPLEMENTATION.md, and create any other documents EXCEPT those mentioned explicitly" — research output is deliberately walled off from the project's core docs. - "Follow tree-of-thoughts pattern and analyze at least 3 options" — a single correct-looking option still fails the skill's contract. - "Fall back to anecdotal references, but call this out EXPLICITLY!" — anecdote is permitted only with a loud disclaimer, never silently blended with reputable sources. -- "MUST use DeepWiki and Context7" — a named-tool mandate written into the generated research prompt, not a suggestion. +- "MUST use DeepWiki and Context7 when available" — a named-tool mandate written into the generated research prompt, conditional on the tools being installed. - "MUST think about and align consequences and consequences of consequences to prevent oversight" — second-order-effects analysis is required of the crafted prompt, not optional depth. ## Invariants — do not change @@ -25,7 +25,7 @@ Single flat SKILL.md, no `assets/` or `references/`. Flow: `` (senior rese - `description` is one dense sentence under the ~25-token budget ("To run systematic deep research via meta-prompting — grounded references, incremental tracking, self-validation."). - XML section names ``, ``, ``, ``, `` are structural anchors that other tooling may parse. - Two distinct, similarly-named state files: `research-state.md` (this skill, `agents/researcher.md`) is the skill-level tracker; `research-flow-state.md` (`commands/research-flow.md`) is the workflow-level tracker — do not rename either without checking both call sites, and do not assume they are the same file. -- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:51` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. +- Inbound couplings: `agents/researcher.md:33,40` ("Apply `research` skill." / "USE SKILL research") — the subagent contractually required to run this skill; `commands/research-flow.md:50` ("Required skills: `research`", phase 3 `execute_research`) — the sanctioned entry point; `skills/orchestration/assets/o-team-manager.md:9` ("USE SKILL `research` for external knowledge if needed") — an ad hoc invocation path outside `research-flow`; `commands/self-help-flow.md:53` — documents direct `/research` invocation as bypassing the structured workflow. ## Editing guide Safe to edit: wording inside the "Research rules" / "Enforcement rules for the generated research prompt" bullet lists, as long as the meta-prompting split survives (this skill governs how research is carried out; the crafted prompt separately carries its own 5 enforcement rules). Handle with care: frontmatter (`name`, `description`), the two state-file names, and the `docs/-research.md` / `research-prompt.md` output paths, since `research-flow.md` and `researcher.md` branch on these exact strings. Referenced by: `agents/researcher.md`, `commands/research-flow.md`, `skills/orchestration/assets/o-team-manager.md`, and `commands/self-help-flow.md` (as a cautionary example). diff --git a/plugins/core-cursor/skills/research/SKILL.md b/plugins/core-cursor/skills/research/SKILL.md index eb7a515ea..bd2376e68 100644 --- a/plugins/core-cursor/skills/research/SKILL.md +++ b/plugins/core-cursor/skills/research/SKILL.md @@ -50,7 +50,7 @@ Research rules: Enforcement rules for the generated research prompt: 1. MUST use todo tasks -2. MUST use DeepWiki and Context7 +2. MUST use DeepWiki and Context7 when available 3. MUST create and update state md file after each task 4. MUST output result file section by section as soon as each section becomes available 5. MUST think about and align consequences and consequences of consequences to prevent oversight (example: doing X leads to Y, which affects Z, thus it should be done ABC way)