agentme 0.36.0 → 0.37.0

package/.xdrs/agentme/edrs/principles/skills/{151-refine-user-story → refine-user-story}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 151-refine-user-story
+name: refine-user-story
 description: >
   Refine, elaborate, study or develop the contents of a user story used to create a unit of work
   for an agile team. Use when you need to write, refine, clarify requirements, ask follow-up
@@ -12,7 +12,7 @@ metadata:
 
 ## Overview
 
-Turns a vague request or rough draft into an implementation-ready user story by running a structured 9-phase refinement process: establishing initiative context and gathering external information to ground the analysis (Phase 1), analysing the request and qualifying requirements with a scope size check (Phase 2), researching existing context and drafting a story skeleton (Phase 3), checking consistency and scope completeness (Phase 4), validating visually with a user journey diagram (Phase 5), challenging from 9 user-perspective angles (Phase 6), challenging from 8 implementer-perspective angles (Phase 7), producing a final ready-to-implement story with a readiness checklist (Phase 8), and running a final readiness double-check (Phase 9).
+Turns a vague request or rough draft into an implementation-ready user story via a structured 9-phase process: initiative context and external information gathering (Phase 1); request analysis and requirements qualification (Phase 2); context research and story drafting (Phase 3); consistency and scope review (Phase 4); visual validation via a user journey diagram (Phase 5); a 9-angle user-perspective challenge (Phase 6); an 8-angle implementer-perspective challenge (Phase 7); final story output with a readiness checklist (Phase 8); and a final readiness re-validation (Phase 9).
 
 Activate when:
 - The request is vague, incomplete, or internally inconsistent.
@@ -298,14 +298,7 @@ After all 9 angles converge, use `vscode_askQuestions` (per Phase gate UI rule)
 
 ### Phase 7: Implementer-Perspective Challenge
 
-For each angle, apply the following protocol. The Phase navigation rule (convergence, Skip, Backtracking) governs loop control on top of this protocol.
-
-1. Generate 10–20 specific questions about that angle **in the context of this story** (grounded in what has been gathered, not generic).
-2. Attempt to answer each question from the current story contents.
-3. For every question that cannot be answered, is unanswered, or reveals a gap or inconsistency: elaborate the finding and ask the user via `vscode_askQuestions`.
-4. Apply the Context Probe rule: if any gap could be resolved by an external spec, API reference, interface contract, or other artifact, ask for it specifically.
-5. Only mark the angle complete when all questions are answered or explicitly deferred as named risks.
-6. Do not resolve choice points unilaterally.
+For each angle, apply the same per-angle protocol defined in Phase 6: generate 10–20 questions about that angle grounded in the current story contents (not generic); attempt to answer each from what has been gathered; for every unanswered question or one that reveals a gap, ask the user via `vscode_askQuestions`; apply the Context Probe rule using implementer-relevant artifacts (an external spec, API reference, interface contract, or similar) when a gap could be resolved by one; mark the angle complete only when every question is answered or explicitly deferred as a named risk; and never resolve a choice point unilaterally. The Phase navigation rule (convergence, Skip, Backtracking) governs loop control on top of this protocol.
 
 **1. Verifiable acceptance criteria**
 Can every acceptance criterion be independently tested by a developer without ambiguity? Is "done" unambiguous for each item, with no subjective interpretation required? Are criteria specific enough to write automated tests against?
@@ -504,4 +497,4 @@ Apply the same 4 criteria from Phase 2 Step 3. If two or more are met, the story
 
 - [`agentme-edr-012`](../../012-continuous-xdr-enrichment.md) — Continuous XDR enrichment policy
 - [`agentme-edr-017`](../../017-skill-testing.md) — Skill testing mandate
-- [`agentme-bdr-401`](../../../../bdrs/operations/401-epic-feature-story-planning.md) — Epic/feature/user story planning structure (policy source for the inline reference in Phase 1)
+- [`agentme-bdr-401`](../../../../bdrs/operations/401-plan-epic-feature-story.md) — Epic/feature/user story planning structure (policy source for the inline reference in Phase 1)

package/.xdrs/agentme/edrs/principles/skills/{151-refine-user-story → refine-user-story}/SKILL.test.md

@@ -1,5 +1,5 @@
 ---
-skill: 151-refine-user-story
+skill: refine-user-story
 skill-version: "4.1"
 ---
 
@@ -8,7 +8,7 @@ skill-version: "4.1"
 ### Scenario 1: Vague request refined into a single story
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "We need to add notifications to the app."
 
@@ -40,7 +40,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 2: User refuses to answer a clarifying question
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "Add export to PDF for the reports page."
 
@@ -62,7 +62,7 @@ The skill asks: "Should the export include all report data or only the currently
 ### Scenario 3: Request too large — split into vertical slices, one refined, rest deferred
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "Build a complete user authentication system: registration with email/password, login, password reset via email, and social login with Google."
 
@@ -102,7 +102,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 4: Phase gate re-run — user requests deeper pass on Phase 4
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The skill has completed Phase 4 (Consistency & Scope Review) and presents the phase gate. The user selects:
+You are an agent with the `refine-user-story` skill loaded. The skill has completed Phase 4 (Consistency & Scope Review) and presents the phase gate. The user selects:
 
 "Re-run Phase 4: Consistency & Scope Review — deeper pass"
 
@@ -129,7 +129,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The skill has co
 ### Scenario 5: Phase 6 user-perspective challenge surfaces a missing journey step
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The story being refined is:
+You are an agent with the `refine-user-story` skill loaded. The story being refined is:
 
 "Add a CSV export button to the reports page so registered users can download the current view."
 
@@ -157,7 +157,7 @@ Phases 1–5 are complete. The skill is running Phase 6, angle 1 (User journey c
 ### Scenario 6: Initiative document with pending placeholder stories — user picks one to refine
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The user references an epic initiative document at `.xdrs/_local/bdrs/operations/initiatives/001-epic-improve-checkout.md`. The initiative contains:
+You are an agent with the `refine-user-story` skill loaded. The user references an epic initiative document at `.xdrs/_local/bdrs/operations/initiatives/001-epic-improve-checkout.md`. The initiative contains:
 
 ```
 ### Milestone 1: Payment Speed
@@ -195,7 +195,7 @@ Each `.assets/userstory-*.md` file contains `**Status:** to-be-refined` plus any
 ### Scenario 7: Refined story output writes asset file and updates initiative Milestone link
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. Phase 0 has detected an active initiative doc at `.xdrs/_local/bdrs/operations/initiatives/002-epic-onboarding.md` with Milestone 1: "First Login Experience". The user is refining a new story to be placed there.
+You are an agent with the `refine-user-story` skill loaded. Phase 0 has detected an active initiative doc at `.xdrs/_local/bdrs/operations/initiatives/002-epic-onboarding.md` with Milestone 1: "First Login Experience". The user is refining a new story to be placed there.
 
 After completing Phases 1–6, Phase 8 produces the final story: "Show personalised welcome screen on first login".
 
@@ -216,7 +216,7 @@ After completing Phases 1–6, Phase 8 produces the final story: "Show personali
 ### Scenario 8: No XDRS scope — skill asks where to save and defaults to workspace root
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "I need to refine a story: users should be able to reset their PIN via SMS."
 
@@ -237,7 +237,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 9: Story lacking detailed specs is flagged and sent back for more refinement
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user is refining:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user is refining:
 
 "Integrate with the payments provider so users can pay by card."
 
@@ -261,7 +261,7 @@ After Phase 2 Step 1, no API endpoints, no payload structures, no documentation
 ### Scenario 10: XDRS scope active, start fresh, story split — Phase 8 asks where to put deferred slices
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. Phase 0 detected an XDRS scope with two existing epic initiatives but the user chose "start fresh — no initiative context". During Phase 2, the story is found to be too large and split into three slices. The user accepts the split and starts refining Slice 1.
+You are an agent with the `refine-user-story` skill loaded. Phase 0 detected an XDRS scope with two existing epic initiatives but the user chose "start fresh — no initiative context". During Phase 2, the story is found to be too large and split into three slices. The user accepts the split and starts refining Slice 1.
 
 **Expected Behaviour**
 1. Phase 0 detects XDRS scope, presents epic initiative list plus "Start fresh" option, user picks "Start fresh".
@@ -280,7 +280,7 @@ You are an agent with the `151-refine-user-story` skill loaded. Phase 0 detected
 ### Scenario 11: Very large story split into multiple slices — no XDRS scope — deferred slices saved to TODO.md
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "I need to build the entire checkout flow: cart review, address selection, payment method entry, coupon validation, order summary, fraud check, payment processing, order confirmation email, and post-purchase upsell screen."
 
@@ -311,7 +311,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 - [ ] The remaining slices appear in a Deferred Items summary at Phase 8.
 - [ ] `vscode_askQuestions` is used at Phase 8 to ask where to save deferred slices (not silently appended).
 - [ ] TODO.md is created (or appended to) at the workspace root with a `## Deferred Stories` section containing a single `### Group:` heading for this split.
-- [ ] The Group heading records the origin (151-refine-user-story, Phase 2 Step 3), the original checkout-flow objective, and the split rationale.
+- [ ] The Group heading records the origin (refine-user-story, Phase 2 Step 3), the original checkout-flow objective, and the split rationale.
 - [ ] Each of the 5 deferred slices appears as its own `#### ` subsection with Objective, Scope, Context captured so far, and a Suggested prompt to resume.
 - [ ] The final output contains exactly one refined story (Slice 1), not all slices.
 - [ ] Skill does NOT offer TODO.md for deferred items from an active initiative doc (this scenario has no initiative doc — condition satisfied).
@@ -321,7 +321,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 12: Phase 6 passes cleanly but Phase 7 implementer angles surface missing error paths and a security concern
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. Phases 1–6 have completed for:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. Phases 1–6 have completed for:
 
 "Allow users to link their Google account to an existing account so they can sign in with Google."
 
@@ -360,7 +360,7 @@ Phase 6 converged without surfacing major gaps. The skill is now entering Phase
 ### Scenario 13: Context Enrichment — existing CRM system, domain inferred, URL provided, mid-phase probe fires
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "Delete contacts from Leads."
 
@@ -397,7 +397,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 14: Context Enrichment — new feature, no codebase, user pastes KR + interview excerpt, loop converges in 2 rounds
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "We need a way for field technicians to report equipment failures from their mobile device."
 
@@ -431,7 +431,7 @@ You are an agent with the `151-refine-user-story` skill loaded. The workspace ha
 ### Scenario 15: Context Enrichment — user skips entirely, Phase 2 proceeds, no fabrication
 
 **Trigger / Input**
-You are an agent with the `151-refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
+You are an agent with the `refine-user-story` skill loaded. The workspace has no `.xdrs/` directory. The user says:
 
 "Add a dark mode toggle to the settings page."
 

package/.xdrs/agentme/edrs/principles/skills/{400-pr-owner-assistant → resolve-pr-comments}/Makefile

@@ -4,5 +4,5 @@ MISE := mise exec --
 .PHONY: test
 
 test:
-	@echo ">>> .xdrs/agentme/edrs/principles/skills/400-pr-owner-assistant: $@"
+	@echo ">>> .xdrs/agentme/edrs/principles/skills/resolve-pr-comments: $@"
 	$(MISE) node --test scripts/*.test.js