agentleFS
danielvm-gitdanielvm-git/bigpowers/skills/survey-context/SKILL.md

survey-context

Skill292 starsChanged 11 days agoMITView on GitHub

Per-task context bootstrap — reads existing specs/ and tech-architecture docs to map the current lifecycle phase and suggest the next skill. Use at the start of any task, when returning after a break, or when unsure what to do next. For deriving a tech-stack doc from scratch, use map-codebase first.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the project's current state and give a phase map + next-skill recommendation.

    line 12
  2. Very specific:

    If CONVENTIONS.md exists at the project root, read it first.

    line 26
  3. Distinctive:

    If CLAUDE.md exists at the project root, read it for project context (stack, commands, architecture, conventions).

    line 55
  4. Very specific:

    Read state.yaml vcs.kind (or resolve auto).

    line 59
  5. Very specific:

    Prefer specs/state.yaml active_flow and handoff.next_skill when present.

    line 87
  6. Distinctive:

    If something looks wrong:

    line 112

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- story: e82s02 -->

Survey Context

Read the project's current state and give a phase map + next-skill recommendation. This is the "where am I?" skill — run it at the start of every task.

Use this vs map-codebase: survey-context consumes existing specs and docs (fast; does not re-derive). map-codebase builds the tech-stack doc from scratch by scanning the codebase. Run map-codebase when specs/tech-architecture/tech-stack.md doesn't exist yet; run survey-context when it does.

HARD GATE — Read specs/ files before suggesting next steps. If state.yaml is stale or contradicts the codebase, request clarification rather than assuming intent.

Orchestrate-project 6 phases: Phase 1 Discover - Phase 2 Elaborate - Phase 3 Plan - Phase 4 Build - Phase 5 Verify - Phase 6 Release

Process

Timing: bash scripts/bp-timing.sh start survey-context at invocation; bash scripts/bp-timing.sh end survey-context before handoff.

1. Read CONVENTIONS.md

If CONVENTIONS.md exists at the project root, read it first. It contains the rules all agents must follow in this project.

2. Read specs/ (YAML-first)

Scan the specs/ directory if it exists:

specs/
├── state.yaml                  → session: active_flow, epic, git, handoff
├── release-plan.yaml           → target version, WSJF epic index
├── execution-status.yaml       → flat story/epic status
├── planning-status.yaml        → discover-phase checklist (optional)
├── requirements/
│   ├── VISION_LATEST.yaml
│   ├── SCOPE_LATEST.yaml
│   └── GLOSSARY_LATEST.yaml
├── plans/                      → TECH_STACK, TEST_PLAN, etc.
├── epics/                      → eNN shards (flat yaml or eNN/stories/)
└── bugs/                       → BUG-*.md + registry.yaml

For each YAML file found, note: exists? keys populated? handoff.next_skill?

Legacy markdown (specs/archive/STATE.md, RELEASE-PLAN.md) is not SoT if YAML exists.

→ verify: bash scripts/validate-specs-yaml.sh

3. Read CLAUDE.md

If CLAUDE.md exists at the project root, read it for project context (stack, commands, architecture, conventions).

4. Check VCS state

Read state.yaml vcs.kind (or resolve auto). Use native identity:

# Git
git status --short; git log --oneline -5; git branch --show-current
# Jujutsu
jj status; jj log -r 'mine() & ::@' -n 5

For Jujutsu, compare stable change IDs and bookmarks with the vcs block; never interpret colocated Git's detached HEAD as branch state.

5. Map the lifecycle phase

Based on what you've found, identify which PMBOK phase this project is currently in:

PhaseSignals
DiscoverNo requirements/SCOPE_LATEST.yaml yet, or only rough notes
DesignSCOPE exists but no release-plan.yaml
Planrelease-plan.yaml exists; on main/master branch
InitiateOn a feature branch; no code changes yet
Executestate.yaml active_flow: build_epic; epic capsule in progress
VerifyImplementation done; run verify-work or run-evals
Bugstate.yaml active_flow: fix_bug or open specs/bugs/BUG-*.md
ReviewAll code written; no PR yet
IntegratePR open; tests passing
SustainOngoing; no active task

Prefer specs/state.yaml active_flow and handoff.next_skill when present.

6. Suggest next skill

Based on the phase and state, recommend the most useful next step:

  • If in Plan/Bug phase and on main: Suggest kickoff-branch next.
  • If in Initiate phase: Suggest develop-tdd or execute-plan or ship-epic.
  • If in Execute phase: Suggest ship-epic (resume) or develop-tdd for active_story_id.
  • If in Verify phase: Suggest verify-work (UAT) or run-evals.

Example:

Phase: Execute
Active branch: feat/e02-verify (state.yaml matches)
release-plan.yaml: v3.0.0, 10 epics
active_epic_id: e02

Suggested next: ship-epic (resume e02s01 at develop-tdd)

Be specific — name the exact skill and why. If multiple options exist, list them in priority order.

7. Surface blockers

If something looks wrong:

  • Broken tests in the baseline
  • Open specs/bugs/BUG-*.md with no active fix branch
  • Epic shards missing verify: on tasks
  • validate-specs-yaml.sh fails
  • Git hash in state.yaml stale vs git rev-parse

Report blockers first, before recommendations.

8. Record story start timestamp

At story start, write metrics.story_start with the current ISO 8601 timestamp to specs/state.yaml as an informational progress marker only — not a measurement input. Cycle-time metrics are now derived from git commit history via scripts/record-cycle-time.sh (see skills/release-branch/REFERENCE.md §Cycle-time recording).

Utility outputs

list-epics (absorbed)

Loop through all specs/epics/*/epic.yaml files and print a summary of story counts per epic. Useful for understanding overall project scope and epic distribution.

check-gates (absorbed)

Print active_flow, validate YAML, then show git status or jj status according to vcs.kind. Use before handoffs or context transitions.

Handoff

Gate: READY -> next: plan-work Writes: state.yaml handoff.next_skill = plan-work

<!-- story: e03s03 -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.