@leeovery/claude-technical-workflows 2.1.17 → 2.1.19

package/skills/start-specification/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: start-specification
-description: "Start a specification session from existing discussions. Discovers available discussions, offers consolidation assessment for multiple discussions, and invokes the technical-specification skill."
+description: "Start a specification session from concluded discussions. Discovers available discussions, offers consolidation assessment for multiple discussions, and invokes the technical-specification skill."
 disable-model-invocation: true
 allowed-tools: Bash(.claude/skills/start-specification/scripts/discovery.sh), Bash(mkdir -p docs/workflow/.cache), Bash(rm docs/workflow/.cache/discussion-consolidation-analysis.md)
 ---
@@ -44,7 +44,7 @@ Follow these steps EXACTLY as written. Do not skip steps or combine them. Presen
 
 Invoke the `/migrate` skill and assess its output.
 
-**If files were updated**: STOP and wait for the user to review the changes (e.g., via `git diff`) and confirm before proceeding to Step 1. Do not continue automatically.
+**If files were updated**: STOP and wait for the user to review the changes (e.g., via `git diff`) and confirm before proceeding to Step 1.
 
 **If no updates needed**: Proceed to Step 1.
 
@@ -64,22 +64,13 @@ If YAML content is already displayed, it has been run on your behalf.
 
 Parse the discovery output to understand:
 
-**From `discussions` array:**
-- Each discussion's name, status, and whether it has an individual specification
-- If `has_individual_spec` is true, `spec_status` contains the spec's status (in-progress/concluded)
+**From `discussions` array:** Each discussion's name, status, and whether it has an individual specification.
 
-**From `specifications` array:**
-- Each specification's name, status, sources, and superseded_by (if applicable)
-- Specifications with `status: superseded` should be noted but excluded from active counts
+**From `specifications` array:** Each specification's name, status, sources, and superseded_by (if applicable). Specifications with `status: superseded` should be noted but excluded from active counts.
 
-**From `cache` section:**
-- `status` - one of three values:
-  - `"valid"` - cache exists and checksums match (safe to load)
-  - `"stale"` - cache exists but discussions have changed (needs re-analysis)
-  - `"none"` - no cache file exists
-- `reason` - explanation of the status
-- `generated` - when the cache was created (null if none)
-- `anchored_names` - grouping names that have existing specifications and MUST be preserved in any regeneration
+**From `cache` section:** `status` (valid/stale/none), `reason`, `generated`, `anchored_names`.
+
+**From `current_state`:** `concluded_count`, `spec_count`, `has_discussions`, `has_concluded`, `has_specs`, and other counts/booleans for routing.
 
 **IMPORTANT**: Use ONLY this script for discovery. Do NOT run additional bash commands (ls, head, cat, etc.) to gather state - the script provides everything needed.
 
@@ -89,763 +80,33 @@ Parse the discovery output to understand:
 
 ## Step 2: Check Prerequisites
 
-#### If no discussions exist
-
-```
-No discussions found in docs/workflow/discussion/
-
-The specification phase requires a completed discussion. Please run /start-discussion first to document the technical decisions, edge cases, and rationale before creating a specification.
-```
-
-**STOP.** Wait for user acknowledgment. Do not proceed.
-
-#### If discussions exist but none are concluded
-
-```
-No concluded discussions found.
-
-The following discussions are still in progress:
-  - {topic-1} (in-progress)
-  - {topic-2} (in-progress)
-
-Please complete the discussion phase before creating specifications. Run /start-discussion to continue a discussion.
-```
+#### If has_discussions is false or has_concluded is false
 
-**STOP.** Wait for user acknowledgment. Do not proceed.
+→ Load **[display-blocks.md](references/display-blocks.md)** and follow its instructions. **STOP.**
 
 #### Otherwise
 
-At least one concluded discussion exists.
-
 → Proceed to **Step 3**.
 
 ---
 
-## Step 3: Present Status & Route
-
-Show the current state clearly. Use this EXACT format:
-
-```
-Specification Phase
-
-Available discussions:
-  + {topic-1} - create new spec
-  + {topic-2} - create new spec
-  ▶ {topic-3} - continue in-progress spec
-  > {topic-4} - review concluded spec
-
-Not specifiable discussions:
-  · {topic-5} [in-progress]
-
-Existing specifications:
-  • {spec-1} [active] - sources: {topic-1}
-  • {spec-2} [superseded → {other-spec}] - sources: {topic-x}
-
-{N} concluded discussions available.
-```
-
-**Legend:**
-- `+` = concluded, no spec yet (create new)
-- `▶` = concluded, has in-progress spec (continue)
-- `>` = concluded, has concluded spec (review)
-- `·` = in-progress (not specifiable)
-
-Omit either discussions section if it has no entries.
-
-#### Routing Based on State
-
-#### If only ONE concluded discussion exists
-
-This is the simple path - no choices needed.
-
-```
-Single concluded discussion found: {topic}
-{If has spec: "An existing specification ({spec_status}) will be continued/refined."}
-
-Proceeding with this discussion.
-```
-
-→ Skip to **Step 9: Confirm Selection** with that discussion as the source.
-
-#### If MULTIPLE concluded discussions exist with NO existing specifications
-
-Check `cache.status` from discovery.
-
-##### If `cache.status: "valid"`
-
-```
-{N} concluded discussions found.
-
-Previous analysis available from {cache.generated}. Loading groupings...
-```
-
-→ Skip directly to **Step 7: Present Grouping Options**.
-
-##### If `cache.status: "stale"`
-
-```
-{N} concluded discussions found.
-
-Note: A previous grouping analysis exists but is now outdated - discussion documents have changed since it was created. Re-analysis is required, but existing specification names will be preserved where groupings overlap.
-
-Analyzing discussions for natural groupings...
-```
-
-→ Proceed to **Step 4: Gather Analysis Context**.
-
-##### If `cache.status: "none"`
-
-```
-{N} concluded discussions found.
-
-Analyzing discussions for natural groupings...
-```
-
-→ Proceed to **Step 4: Gather Analysis Context**.
-
-#### If MULTIPLE concluded discussions exist WITH existing specifications
-
-Check `cache.status` from discovery to determine which options to present.
-
-##### If `cache.status: "valid"`
-
-```
-· · ·
-
-What would you like to do?
-
-- **`c`/`continue`** — Resume work on a spec in progress
-- **`s`/`select`** — Choose from previously analyzed groupings ({cache.generated})
-- **`r`/`refresh`** — Fresh analysis of discussion relationships
-```
-
-**STOP.** Wait for user response.
-
-##### If `cache.status: "stale"`
-
-```
-· · ·
-
-What would you like to do?
-
-Note: A previous grouping analysis exists but is now outdated - discussion documents have changed since it was created. Re-analysis is required, but existing specification names will be preserved where groupings overlap.
-
-- **`c`/`continue`** — Resume work on a spec in progress
-- **`a`/`assess`** — Re-analyze discussions for combinations
-```
-
-**STOP.** Wait for user response.
-
-##### If `cache.status: "none"`
-
-```
-· · ·
-
-What would you like to do?
-
-- **`c`/`continue`** — Resume work on a spec in progress
-- **`a`/`assess`** — Analyze discussions for combinations
-```
-
-**STOP.** Wait for user response.
-
-#### If "continue"
-
-```
-Which specification would you like to continue?
-
-1. {spec-1} ({status}) - sources: {topics}
-2. {spec-2} ({status}) - sources: {topics}
-```
-
-**STOP.** Wait for user to pick, then skip to **Step 9**.
-
-#### If "select" (valid cache path)
-
-Load groupings from cache and → Skip directly to **Step 7: Present Grouping Options**.
-
-(Context was already gathered when the analysis was created - no need to ask again.)
-
-#### If "refresh"
-
-Delete the existing cache to force regeneration:
-```bash
-rm docs/workflow/.cache/discussion-consolidation-analysis.md
-```
-
-→ Proceed to **Step 4: Gather Analysis Context**.
-
-#### If "assess" (no valid cache path)
-
-→ Proceed to **Step 4: Gather Analysis Context**.
-
----
-
-## Step 4: Gather Analysis Context
-
-```
-Before I analyze the discussions, is there anything about your project structure or how these topics relate that would help me group them appropriately?
-
-For example:
-- Are certain topics part of the same feature or subsystem?
-- Are there dependencies I should know about?
-- Any topics that MUST stay separate?
-```
-
-**STOP.** Wait for user response. Note their input for the analysis.
-
-→ Proceed to **Step 5**.
-
----
-
-## Step 5: Check Cache Status
+## Step 3: Route
 
-Check `cache.status` from discovery.
+Based on discovery state, load exactly ONE reference file:
 
-#### If `cache.status: "valid"`
+#### If concluded_count == 1
 
-```
-Using cached analysis
-
-Discussion documents unchanged since last analysis ({cache.generated}).
-Loading previously identified groupings...
-```
+→ Load **[display-single.md](references/display-single.md)** and follow its instructions.
 
-Load groupings from cache and → Skip to **Step 7: Present Grouping Options**.
-
-#### If `cache.status: "stale"` or `"none"`
-
-```
-{cache.reason}
-
-Analyzing discussions...
-```
-
-→ Proceed to **Step 6: Analyze Discussions**.
-
----
-
-## Step 6: Analyze Discussions
-
-**This step is critical. You MUST read every concluded discussion document thoroughly.**
-
-For each concluded discussion:
-1. Read the ENTIRE document using the Read tool (not just frontmatter)
-2. Understand the decisions, systems, and concepts it defines
-3. Note dependencies on or references to other discussions
-4. Identify shared data structures, entities, or behaviors
-
-Then analyze coupling between discussions:
-- **Data coupling**: Discussions that define or depend on the same data structures
-- **Behavioral coupling**: Discussions where one's implementation requires another
-- **Conceptual coupling**: Discussions that address different facets of the same problem
-
-Group discussions into specifications where each grouping represents a **coherent feature or capability that can be independently planned and built** — with clear stages delivering incremental, testable value. Coupling tells you what's related; the grouping decision also requires that the result is the right shape:
-
-- **Tightly coupled discussions belong together** — their decisions are inseparable and would produce interleaved implementation work
-- **Don't group too broadly** — if a grouping mixes unrelated concerns, the resulting specification will produce incoherent stages and tasks that jump between disconnected areas
-- **Don't group too narrowly** — if a grouping is too thin, it may not warrant its own specification, planning, and implementation cycle
-- **Flag cross-cutting discussions** — discussions about patterns or policies (not features) should become cross-cutting specifications rather than being grouped with feature discussions
-
-#### Preserve Anchored Names
-
-**CRITICAL**: Check the `cache.anchored_names` from discovery state. These are grouping names that have existing specifications.
-
-When forming groupings:
-- If a grouping contains a majority of the same discussions as an anchored name's spec, you MUST reuse that anchored name
-- Only create new names for genuinely new groupings with no overlap
-- If an anchored spec's discussions are now scattered across multiple new groupings, note this as a **naming conflict** to present to the user
-
-#### Save to Cache
-
-After analysis, create the cache directory if needed:
-```bash
-mkdir -p docs/workflow/.cache
-```
+#### If cache status is "valid"
 
-Write to `docs/workflow/.cache/discussion-consolidation-analysis.md`:
-
-```markdown
----
-checksum: {checksum from current_state.discussions_checksum}
-generated: {ISO date}
-discussion_files:
-  - {topic1}.md
-  - {topic2}.md
----
-
-# Discussion Consolidation Analysis
-
-## Recommended Groupings
-
-### {Suggested Specification Name}
-- **{topic-a}**: {why it belongs in this group}
-- **{topic-b}**: {why it belongs in this group}
-- **{topic-c}**: {why it belongs in this group}
-
-**Coupling**: {Brief explanation of what binds these together}
-
-### {Another Specification Name}
-- **{topic-d}**: {why it belongs}
-- **{topic-e}**: {why it belongs}
-
-**Coupling**: {Brief explanation}
-
-## Independent Discussions
-- **{topic-f}**: {Why this stands alone - no strong coupling to others}
-
-## Analysis Notes
-{Any additional context about the relationships discovered}
-{Note any naming conflicts with anchored specs here}
-```
-
-→ Proceed to **Step 7**.
-
----
-
-## Step 7: Present Grouping Options
-
-Present the groupings with FULL status information.
-
-For each grouping, show:
-- The grouping name
-- Whether a specification already exists for this grouping (and its effective status)
-- Each discussion in the grouping and its incorporation status
-
-### Determining Discussion Status Within a Grouping
-
-For each grouping, first check if a grouped specification exists:
-1. Convert the grouping name to kebab-case (lowercase, spaces to hyphens)
-2. Check if `docs/workflow/specification/{kebab-name}.md` exists
-3. If it exists, get its `sources` array from the discovery output
-
-The sources array uses object format with explicit status tracking:
-```yaml
-sources:
-  - name: topic-a
-    status: incorporated
-  - name: topic-b
-    status: pending
-```
-
-**If a grouped spec exists for the grouping:**
-
-For each discussion in the grouping:
-1. Look up the discussion in the spec's `sources` array (by `name` field)
-2. If found → use the source's `status` field (`incorporated` or `pending`)
-3. If NOT found → status is `"pending"` (new source not yet added to spec)
-
-Calculate the **effective spec status**:
-- If ALL discussions in the grouping have `status: incorporated` → use the spec's actual status from file
-- If ANY discussion has `status: pending` OR is not in sources → effective status is `"needs update"`
-
-**If NO grouped spec exists:**
-
-For each discussion in the grouping:
-- If the discussion has an individual spec (`has_individual_spec: true`) → status is `"spec: {spec_status}"`
-- If the discussion has no spec → status is `"ready"`
-
-**Format:**
-
-```
-{Fresh analysis / Cached analysis} complete
-
-Recommended Groupings:
-
-### 1. {Grouping Name} (spec: {effective_status})
-| Discussion | Status |
-|------------|--------|
-| {topic-a} | incorporated |
-| {topic-b} | incorporated |
-| {topic-c} | pending |
-
-Coupling: {explanation}
-
-### 2. {Another Grouping}
-| Discussion | Status |
-|------------|--------|
-| {topic-d} | ready |
-| {topic-e} | spec: in-progress |
-
-Coupling: {explanation}
-
-### Independent
-- {topic-f}: standalone
-
----
-
-· · ·
-
-How would you like to proceed?
-
-- **`p`/`proceed`** — As recommended (I'll ask which to start with)
-- **`s`/`single`** — Consolidate ALL into one unified spec
-- **`i`/`individual`** — Create 1:1 specs (I'll ask which to start)
-- **`r`/`refresh`** — Re-analyze discussions
-- Combine differently — tell me your preferred groupings
-```
+→ Load **[display-groupings.md](references/display-groupings.md)** and follow its instructions.
 
-**Status Legend:**
-- `incorporated` - Discussion content has been woven into the grouped specification
-- `pending` - Discussion is part of the group but not yet incorporated into the spec
-- `ready` - Discussion has no spec yet (ready to be specified)
-- `spec: {status}` - Discussion has its own individual specification
-- `needs update` - Grouped spec exists but has pending sources to incorporate
+#### If spec_count == 0 and cache is "none" or "stale"
 
-**STOP.** Wait for user to choose.
+→ Load **[display-analyze.md](references/display-analyze.md)** and follow its instructions.
 
-→ Based on choice, proceed to **Step 8**.
-
----
-
-## Step 8: Select Grouping
-
-Based on user's choice from Step 7:
-
-#### If "proceed"
-
-```
-Which would you like to start with?
-
-Grouped:
-1. {Grouping Name A} - {N} discussions
-2. {Grouping Name B} - {N} discussions (spec: {spec_status})
-3. {Grouping Name C} - {N} discussions
-
-Independent:
-4. {topic-f} - standalone
-5. {topic-g} - standalone
-```
-
-List ALL items from the analysis: grouped specifications first, then independent discussions. Number them consecutively.
-
-**STOP.** Wait for user to pick a number, then proceed to **Step 9**.
-
-#### If "combine differently"
-
-```
-Please describe your preferred groupings. Which discussions should be combined together?
-```
-
-**STOP.** Wait for user to describe their groupings.
-
-##### Analyze Impact
-
-Determine which existing specifications are affected by the proposed groupings. A spec is "affected" if:
-- Its source discussions are being split across multiple new groupings, OR
-- It's being merged with another spec's source discussions
-
-##### Simple case (0-1 specs affected)
-
-Establish a name for each grouping:
-- If the grouping contains all sources from an existing spec → suggest that spec's name
-- Otherwise → propose a semantic name based on the combined content
-
-```
-Based on your description:
-
-1. {Proposed Name} - {topic-a}, {topic-b}, {topic-c}
-   {If expanding existing spec: "(continues {spec-name} specification)"}
-
-{If name derived from existing spec:}
-Keep the name "{spec-name}" or use a different name?
-```
-
-**STOP.** Wait for user to confirm or provide a different name.
-
-→ Proceed to **Update Cache** below.
-
-##### Complex case (2+ specs affected)
-
-```
-This reorganization affects multiple existing specifications:
-- {spec-1} (sources: {topics})
-- {spec-2} (sources: {topics})
-
-Moving discussions between established specifications requires deleting the affected specs and re-processing. The source material in your discussions is preserved.
-
-· · ·
-
-- **`d`/`delete`** — Remove affected specs and create fresh ones for your new groupings
-- **`r`/`reconsider`** — Adjust your groupings to affect fewer specs
-```
-
-**STOP.** Wait for user choice.
-
-- If delete: Remove the affected spec files, then proceed to **Update Cache**
-- If reconsider: Return to grouping description prompt
-
-##### Update Cache
-
-After confirming groupings, update the cache to reflect the user's custom arrangement.
-
-Rewrite `docs/workflow/.cache/discussion-consolidation-analysis.md` with:
-- Same `checksum` value (discussions unchanged)
-- New `generated` timestamp
-- User's custom groupings in the "Recommended Groupings" section
-- Note in Analysis Notes: `Custom groupings confirmed by user.`
-
-This ensures subsequent runs present the agreed groupings rather than re-analyzing.
-
-```
-Groupings confirmed. Cache updated.
-
-Which grouping would you like to start with?
-
-1. {Grouping A} - {N} discussions {if has spec: "(spec: {spec_status})"}
-2. {Grouping B} - {N} discussions
-```
-
-**STOP.** Wait for user to pick, then proceed to **Step 9**.
-
-#### If "single"
-
-Use "unified" as the specification name.
-Check if `docs/workflow/specification/unified.md` already exists.
-
-```
-{If exists: "A unified specification already exists. Proceeding will continue/refine it."}
-
-This will consolidate ALL {N} concluded discussions into a single specification.
-
-· · ·
-
-Proceed with unified specification?
-- **`y`/`yes`** — Proceed
-- **`n`/`no`** — Cancel
-```
-
-**STOP.** Wait for user to confirm, then proceed to **Step 9** with all discussions as sources.
-
-#### If "individual"
-
-```
-Which discussion would you like to specify?
-
-1. {topic-1}
-2. {topic-2} (spec: {spec_status})
-3. {topic-3}
-```
-
-**STOP.** Wait for user to pick, then proceed to **Step 9**.
-
-#### If "refresh"
-
-```
-Refreshing analysis...
-```
-
-Delete the cache file:
-```bash
-rm docs/workflow/.cache/discussion-consolidation-analysis.md
-```
-
-→ Return to **Step 6: Analyze Discussions**.
-
----
-
-## Step 9: Confirm Selection
-
-Present what will happen based on the selection:
-
-#### If creating a NEW grouped specification (with individual specs to incorporate)
-
-```
-Creating specification: {grouping-name}
-
-Sources:
-| Type | File | Action |
-|------|------|--------|
-| Discussion | {topic-a}.md | Extract content |
-| Discussion | {topic-b}.md | Extract content |
-| Existing Spec | specification/{topic-c}.md | Incorporate and supersede |
-
-Output: docs/workflow/specification/{grouping-name}.md
-
-After completion:
-- specification/{topic-c}.md will be marked as superseded
-
-· · ·
-
-Proceed?
-- **`y`/`yes`** — Proceed
-- **`n`/`no`** — Go back
-```
-
-#### If creating a NEW grouped specification (no existing specs)
-
-```
-Creating specification: {grouping-name}
-
-Sources:
-- docs/workflow/discussion/{topic-a}.md
-- docs/workflow/discussion/{topic-b}.md
-- docs/workflow/discussion/{topic-c}.md
-
-Output: docs/workflow/specification/{grouping-name}.md
-
-· · ·
-
-Proceed?
-- **`y`/`yes`** — Proceed
-- **`n`/`no`** — Go back
-```
-
-#### If CONTINUING an existing grouped specification
-
-```
-Continuing specification: {grouping-name}
-
-Existing: docs/workflow/specification/{grouping-name}.md (will be refined)
-
-Sources:
-- docs/workflow/discussion/{topic-a}.md
-- docs/workflow/discussion/{topic-b}.md
-
-· · ·
-
-Proceed?
-- **`y`/`yes`** — Proceed
-- **`n`/`no`** — Go back
-```
-
-#### If creating/continuing an INDIVIDUAL specification
-
-```
-{Creating / Continuing} specification: {topic}
-
-Sources:
-- docs/workflow/discussion/{topic}.md
-
-Output: docs/workflow/specification/{topic}.md
-
-· · ·
-
-Proceed?
-- **`y`/`yes`** — Proceed
-- **`n`/`no`** — Go back
-```
-
-**STOP.** Wait for user confirmation.
-
-**If user confirms (y):** → Proceed to **Step 10**.
-**If user declines (n):** → Return to **Step 8** to select a different grouping or discussion.
-
----
-
-## Step 10: Gather Additional Context
-
-```
-Before invoking the specification skill:
-
-1. Any additional context or priorities to consider?
-2. Any constraints or changes since the discussion(s) concluded?
-3. Are there existing partial implementations or related documentation I should review?
-
-(Say 'none' or 'continue' if nothing to add)
-```
-
-**STOP.** Wait for user response.
-
-→ Proceed to **Step 11**.
-
----
-
-## Step 11: Invoke the Skill
-
-After completing all steps above, this skill's purpose is fulfilled.
-
-Invoke the [technical-specification](../technical-specification/SKILL.md) skill for your next instructions. Do not act on the gathered information until the skill is loaded - it contains the instructions for how to proceed.
-
-#### Handoff Format
-
-**Single source (individual specification):**
-
-```
-Specification session for: {topic}
-
-Sources:
-- docs/workflow/discussion/{topic}.md
-
-Output: docs/workflow/specification/{topic}.md
-
-Additional context: {summary of user's answers from Step 10}
-
----
-Invoke the technical-specification skill.
-```
-
-**Multiple sources (grouped specification, no existing specs to incorporate):**
-
-```
-Specification session for: {specification-name}
-
-Sources:
-- docs/workflow/discussion/{topic-1}.md
-- docs/workflow/discussion/{topic-2}.md
-- docs/workflow/discussion/{topic-3}.md
-
-Output: docs/workflow/specification/{specification-name}.md
-
-Additional context: {summary of user's answers from Step 10}
-
----
-Invoke the technical-specification skill.
-```
-
-**Multiple sources WITH existing specs to incorporate:**
-
-```
-Specification session for: {specification-name}
-
-Source discussions:
-- docs/workflow/discussion/{topic-1}.md
-- docs/workflow/discussion/{topic-2}.md
-
-Existing specifications to incorporate:
-- docs/workflow/specification/{topic-3}.md (covers: {topic-3} discussion)
-
-Output: docs/workflow/specification/{specification-name}.md
-
-Context: This consolidates multiple sources. The existing {topic-3}.md specification should be incorporated - extract and adapt its content alongside the discussion material. The result should be a unified specification, not a simple merge.
-
-After the {specification-name} specification is complete, mark the incorporated specs as superseded by updating their frontmatter:
-
-    status: superseded
-    superseded_by: {specification-name}
-
-Additional context: {summary of user's answers from Step 10}
-
----
-Invoke the technical-specification skill.
-```
-
-**Continuing an existing specification:**
-
-```
-Specification session for: {specification-name}
-
-Continuing existing: docs/workflow/specification/{specification-name}.md
-
-Sources for reference:
-- docs/workflow/discussion/{topic-1}.md
-- docs/workflow/discussion/{topic-2}.md
-
-Context: This specification already exists. Review and refine it based on the source discussions and any new context provided.
-
-Additional context: {summary of user's answers from Step 10}
-
----
-Invoke the technical-specification skill.
-```
-
----
+#### Otherwise
 
-## Notes
+→ Load **[display-specs-menu.md](references/display-specs-menu.md)** and follow its instructions.
 
-- Ask questions clearly and STOP after each to wait for responses
-- Only concluded discussions should proceed to specification
-- When multiple sources are provided, the skill will extract exhaustively from ALL of them
-- Attribution in the specification should trace content back to its source discussion(s)
-- Superseded specifications are excluded from future planning phases
-- The specification is the "line in the sand" - be thorough, not hasty