Merge pull request #10 from GrillerGeek/copilot/fix-plugin-hash-id-issue

fix: agent prompts still generating sequential IDs after hash-ID migration

Author: GrillerGeek

plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "idd-framework",
-  "version": "1.2.7",
+  "version": "1.2.8",
   "description": "Intent-Driven Development framework plugin — automates the IDD workflow with role-specific tools for stakeholder interviews, artifact generation, and structured documentation",
   "author": { "name": "GrillerGeek" },
   "homepage": "https://github.com/grillergeek/idd-framework",

plugin/agents/expectation-author.md

@@ -63,7 +63,7 @@ You are the IDD Expectation Author. Your role is to help define verifiable Expec
    - High: Novel domain, many edge cases, integration risk
 
 6. **Generate Artifacts** — For each Expectation:
-   - Generate an Expectation ID (EXP-9b04, incrementing)
+   - Generate an Expectation ID by running `idd-next-id expectation` (e.g., `EXP-9b04`)
    - Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/expectation-template.md`
    - Save to `docs/expectations/[expectation-id].yaml`
    - Update the parent Intention file at `docs/intentions/[intention-id].yaml` to add the new Expectation ID to the `expectations` list

plugin/agents/intention-author.md

@@ -52,7 +52,7 @@ You are the IDD Intention Author. Your role is to guide the Product Owner in dec
    - Identify dependencies between Intentions
 
 4. **Generate Artifacts** — For each Intention:
-   - Generate an Intention ID (INT-7c21, incrementing)
+   - Generate an Intention ID by running `idd-next-id intention` (e.g., `INT-7c21`)
    - Use the template at `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/intention-template.md`
    - Save to `docs/intentions/[intention-id].yaml`
 

plugin/agents/product-interviewer.md

@@ -64,7 +64,7 @@ Use AskUserQuestion for each section. Be conversational but thorough.
 **After the Interview:**
 
 1. Summarize what you captured and present it to the stakeholder for confirmation
-2. Generate a Product ID (PROD-a3f8, incrementing from existing products in `docs/products/`)
+2. Generate a Product ID by running `idd-next-id product` (e.g., `PROD-a3f8`)
 3. Produce the Product artifact using the template at `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/product-template.md`
 4. Save to `docs/products/[product-id].yaml`
 5. Present the artifact to the user and ask if any adjustments are needed

plugin/agents/quick-spec-author.md

@@ -51,7 +51,7 @@ Decompose the feature description into 2-4 outcome-focused Intentions:
 - Assign priorities and identify dependencies
 - Present to the user for quick confirmation/adjustment
 
-Read `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/intention-template.md` for the schema. Generate and save INT-*.yaml files to `docs/intentions/`.
+Read `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/intention-template.md` for the schema. Generate IDs by running `idd-next-id intention` for each artifact. Save INT-*.yaml files to `docs/intentions/`.
 
 ### Phase 3: Define Expectations
 
@@ -61,7 +61,7 @@ For each Intention, define Expectations with edge cases:
 - Enumerate at least 2 edge cases per Expectation (boundary values, error conditions, unusual states)
 - Assess complexity (low/medium/high)
 
-Read `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/expectation-template.md` for the schema. Generate and save EXP-*.yaml files to `docs/expectations/`. After saving Expectations, update each parent Intention file to add the new Expectation IDs to its `expectations` list.
+Read `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/expectation-template.md` for the schema. Generate IDs by running `idd-next-id expectation` for each artifact. Save EXP-*.yaml files to `docs/expectations/`. After saving Expectations, update each parent Intention file to add the new Expectation IDs to its `expectations` list.
 
 ### Phase 4: Author the Spec
 
@@ -84,7 +84,7 @@ Read `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/spec-reference.m
 
 **Validation Block** — Split into automated (tests, type checks, contract checks) and human review (UX, architecture, data accuracy).
 
-Run the completeness checklist. Generate and save SPEC-*.yaml to `docs/specs/`.
+Run the completeness checklist. Generate the Spec ID by running `idd-next-id spec`. Save SPEC-*.yaml to `docs/specs/`.
 
 ### Phase 5: Present Summary
 

plugin/agents/spec-author.md

@@ -55,7 +55,7 @@ You are the IDD Spec Author. Your role is to create AI-ready Specs with all 5 ma
 
 4. **Completeness Check** — Run through the checklist from `${CLAUDE_PLUGIN_ROOT}/skills/idd-orchestration/references/spec-reference.md` and flag any gaps.
 
-5. **Save** — Generate a Spec ID (SPEC-d12e, incrementing) and save to `docs/specs/[spec-id].yaml`.
+5. **Save** — Generate a Spec ID by running `idd-next-id spec` (e.g., `SPEC-d12e`) and save to `docs/specs/[spec-id].yaml`.
 
 6. **Present** — Show the complete Spec to the user for review before finalizing.