@exodus/xqa 1.5.0 → 1.6.0

package/dist/skills/xqa-spec/SKILL.md

@@ -23,12 +23,38 @@ IMPORTANT: Never generate a draft before the interview is complete. The user des
 
 ### 1. Explore
 
-Silently scan `.xqa/specs/*.test.md`. Learn:
+Time budget: complete within 10 tool calls. Do not surface findings yet.
 
-- Naming conventions
-- Level of detail and step granularity
+**a. Existing specs and app context — run in parallel:**
 
-Also read `.xqa/app.md` if it exists for app context.
+MUST issue all of the following as a single parallel batch (one message, multiple tool calls):
+
+- Glob `**/.xqa/specs/*.test.md` → read every result
+- Read `.xqa/app.md` if it exists
+
+Learn from specs: naming conventions, step granularity, level of detail.
+
+**b. Codebase discovery — run in parallel:**
+
+MUST issue all of the following as a single parallel batch:
+
+- Glob `**/*Screen.tsx` | `**/*Screen.ts`
+- Glob `**/screens/**/*.tsx` | `**/screens/**/*.ts`
+- Glob `**/navigation/**` | `**/routes.ts` | `**/routes.tsx` | `**/router.ts`
+- Glob `**/*Navigator.tsx` | `**/*Navigator.ts`
+
+Read every Glob result that returns ≤ 5 files. When a Glob returns > 5 files, read only the first 3 results — prioritise files whose names match the flow the user described.
+
+**c. Feature-specific scan (conditional):**
+
+If the user named a specific feature or screen, run ONE additional parallel batch:
+
+- Grep the feature name across `**/*.tsx`, `**/*.ts` (files with matches only)
+- Grep for copy strings related to the feature in `**/*.ts` | `**/*.tsx` | `**/*.json`
+
+Read up to 3 matching files. Stop.
+
+**Capture silently:** screen names, navigation routes, copy strings, feature flag identifiers. This context is used only during step 3a reminders — never presented to the user unprompted.
 
 ### 2. Detect mode
 
@@ -53,6 +79,21 @@ Ask one question at a time. Wait for the answer before asking the next. Prefer m
 
 IMPORTANT: Ask each question in its own message. Never batch questions.
 
+### 3a. Code-informed reminders (during step collection)
+
+After the user describes a step, you MAY offer AT MOST ONE code-informed follow-up reminder before moving to the next step. Phrase it as:
+
+> "I also see <intent-first phrase> in the code — want to include it as a step? (source: `<file>`)"
+
+Rules:
+
+- Max one unsolicited suggestion per user-described step. No bulk proposals.
+- Declined once → never re-offer that suggestion.
+- Translate code findings into intent-first language BEFORE presenting. Component names, route names, and variable names must be rewritten as user goals.
+- Copy strings belong in `hint:` only — never in the intent phrase.
+- Always cite the source file the suggestion was derived from.
+- If no code-backed reminder is worth offering, stay silent and move on.
+
 ### 4. Draft
 
 Assemble using ONLY these frontmatter fields: `feature`, `timeout`. Do not add any other frontmatter field. `feature` MUST be present. `timeout` MUST be a positive number (seconds) if included.
@@ -153,3 +194,13 @@ Omit `timeout` line if not provided. Omit `## Assertions` section if none. Omit
 - Intent-first language only; no literal `Tap "<label>"` references
 - Write file only after explicit approval
 - In edit mode, ask before touching anything
+
+### Code exploration constraints
+
+- Never present a pre-populated step list derived from code before the user has described the flow
+- Never use component names, route names, or variable names as intent phrases — translate to user-goal language first
+- Never place code-derived text in the intent phrase — copy strings belong in `hint:` only
+- Never re-offer a suggested step after the user declines it once
+- Never propose more than one unsolicited step per user-described step (no bulk suggestions)
+- Always cite the source file when proposing a code-derived reminder
+- Never infer the entire flow from navigation routes or screen stack and present it as a draft