Storytime Survey — Standalone
Run a codebase survey and artifact scan without triggering a full
storytime session. Produces a survey document with coverage fingerprint.
Arguments
Optional focus area or problem context: $ARGUMENTS
Process
1. Check for Prior Surveys
Look for existing survey.md files in specs/.storytime/sessions/*/ or
elsewhere in the repo. If found, read the coverage fingerprint and compute
the delta:
- Commit drift:
git rev-list <prior-commit>..HEAD
- Coverage gaps: paths unvisited in prior survey
- Present to user: resurvey stale, extend to gaps, full resurvey, or trust prior
2. Codebase Scan
Launch an Explore agent to survey the codebase:
- If a focus area was provided, prioritize those paths
- Identify: code structure, patterns, dependencies, constraints
- Note: existing test coverage, build system, deployment setup
3. Artifact Scan
Scan the entire repo for prior work artifacts:
- Specs, docs, design records, agent definitions, team files
- ADRs, RFCs, .kiro files, README files with design rationale
- See the main storytime skill's
references/artifact-scan.md for
full scan targets and classification heuristics
Classify each: team-like, spec-like, config-like, or noise.
4. Present Inventory
Show the artifact inventory as a checklist:
- Each item: checkbox, filename, short description (< 10 words if needed)
- Tag each:
[team] [spec] [config]
- Pre-check items that seem relevant
User can:
- Toggle items, ask about specific files
- Direct instruction ("ignore all the kiro stuff")
- No further action needed — this is just the survey
5. Write Survey Document
Write specs/.storytime/sessions/<topic>/survey.md (storytime-native) or
to the appropriate location for the repo's mode. Include:
If no topic was established, use general or derive from the focus area.
Output
The survey document is the deliverable. The user can then:
- Run
/storytime:storytime with the survey as pre-existing context
- Run
/storytime:consolidate to organize discovered artifacts
- Run
/storytime:absorb to have a team interpret the findings
- Do nothing — the survey stands alone as a codebase snapshot
1---2name: storytime-survey3description: This skill should be used when the user asks to "survey the codebase", "scan for artifacts", "what's in this repo", "inventory the docs", "run a survey", "check coverage", or wants to understand the codebase and existing documents without running a full storytime session. Produces a survey with coverage fingerprint.4---56<!-- version-echo: display "storytime v1.0.1" at start of execution -->7# Storytime Survey — Standalone89Run a codebase survey and artifact scan without triggering a full10storytime session. Produces a survey document with coverage fingerprint.1112## Arguments1314Optional focus area or problem context: $ARGUMENTS1516## Process1718### 1. Check for Prior Surveys1920Look for existing `survey.md` files in `specs/.storytime/sessions/*/` or21elsewhere in the repo. If found, read the coverage fingerprint and compute22the delta:23- Commit drift: `git rev-list <prior-commit>..HEAD`24- Coverage gaps: paths unvisited in prior survey25- Present to user: resurvey stale, extend to gaps, full resurvey, or trust prior2627### 2. Codebase Scan2829Launch an Explore agent to survey the codebase:30- If a focus area was provided, prioritize those paths31- Identify: code structure, patterns, dependencies, constraints32- Note: existing test coverage, build system, deployment setup3334### 3. Artifact Scan3536Scan the entire repo for prior work artifacts:37- Specs, docs, design records, agent definitions, team files38- ADRs, RFCs, .kiro files, README files with design rationale39- See the main storytime skill's `references/artifact-scan.md` for40 full scan targets and classification heuristics4142Classify each: **team-like**, **spec-like**, **config-like**, or noise.4344### 4. Present Inventory4546Show the artifact inventory as a checklist:47- Each item: checkbox, filename, short description (< 10 words if needed)48- Tag each: `[team]` `[spec]` `[config]`49- Pre-check items that seem relevant5051User can:52- Toggle items, ask about specific files53- Direct instruction ("ignore all the kiro stuff")54- No further action needed — this is just the survey5556### 5. Write Survey Document5758Write `specs/.storytime/sessions/<topic>/survey.md` (storytime-native) or59to the appropriate location for the repo's mode. Include:6061- Codebase context summary62- Artifact inventory with classifications and user dispositions63- **Coverage fingerprint** (REQUIRED):64 ```yaml65 fingerprint:66 commit: <HEAD sha>67 branch: <branch>68 paths_scanned: [...]69 paths_skipped: [...]70 paths_unvisited: [...]71 files_examined: <N>72 files_total: <N>73 coverage_ratio: <0.XX>74 artifacts_found: <N>75 artifacts_classified:76 team: <N>77 spec: <N>78 config: <N>79 ```8081If no topic was established, use `general` or derive from the focus area.8283## Output8485The survey document is the deliverable. The user can then:86- Run `/storytime:storytime` with the survey as pre-existing context87- Run `/storytime:consolidate` to organize discovered artifacts88- Run `/storytime:absorb` to have a team interpret the findings89- Do nothing — the survey stands alone as a codebase snapshot
1ps0