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
- kayspiegel/survey-insight-skillstheir own version, first seen Aug 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- kayspiegel/survey-insight-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository162 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- website/AGENTS.mdAGENTS.md
- .cursor/rules/align-grid.mdcCursor rule
- .cursor/rules/assess-impact.mdcCursor rule
- .cursor/rules/audit-code.mdcCursor rule
- .cursor/rules/audit-plan.mdcCursor rule
- .cursor/rules/build-epic.mdcCursor rule
- .cursor/rules/change-request.mdcCursor rule
- .cursor/rules/commit-message.mdcCursor rule
- .cursor/rules/compose-workflow.mdcCursor rule
- .cursor/rules/craft-skill.mdcCursor rule
- .cursor/rules/deepen-architecture.mdcCursor rule
- .cursor/rules/define-language.mdcCursor rule
- .cursor/rules/define-success.mdcCursor rule
- .cursor/rules/delegate-task.mdcCursor rule
- .cursor/rules/deploy.mdcCursor rule
- .cursor/rules/design-interface.mdcCursor rule
- .cursor/rules/develop-tdd.mdcCursor rule
- .cursor/rules/diagnose-root.mdcCursor rule
- .cursor/rules/diagnose-stall.mdcCursor rule
- .cursor/rules/dispatch-agents.mdcCursor rule
- .cursor/rules/edit-document.mdcCursor rule
- .cursor/rules/elaborate-spec.mdcCursor rule
- .cursor/rules/enforce-first.mdcCursor rule
- .cursor/rules/evolve-skill.mdcCursor rule
- .cursor/rules/execute-plan.mdcCursor rule
- .cursor/rules/extract-design.mdcCursor rule
- .cursor/rules/find-way.mdcCursor rule
- .cursor/rules/fix-bug.mdcCursor rule
- .cursor/rules/gate-trace.mdcCursor rule
- .cursor/rules/generate-allure-report.mdcCursor rule
- .cursor/rules/grill-me.mdcCursor rule
- .cursor/rules/grill-with-docs.mdcCursor rule
- .cursor/rules/guard-git.mdcCursor rule
- .cursor/rules/harden-vps.mdcCursor rule
- .cursor/rules/hook-commits.mdcCursor rule
- .cursor/rules/inspect-quality.mdcCursor rule
- .cursor/rules/investigate-bug.mdcCursor rule
- .cursor/rules/kickoff-branch.mdcCursor rule
- .cursor/rules/maintain-wiki.mdcCursor rule
- .cursor/rules/map-codebase.mdcCursor rule
- .cursor/rules/migrate-spec.mdcCursor rule
- .cursor/rules/model-domain.mdcCursor rule
- .cursor/rules/orchestrate-project.mdcCursor rule
- .cursor/rules/organize-workspace.mdcCursor rule
- .cursor/rules/plan-refactor.mdcCursor rule
- .cursor/rules/plan-release.mdcCursor rule
- .cursor/rules/plan-tests.mdcCursor rule
- .cursor/rules/plan-work.mdcCursor rule
- .cursor/rules/publish-package.mdcCursor rule
- .cursor/rules/quick-fix.mdcCursor rule
- .cursor/rules/release-branch.mdcCursor rule
- .cursor/rules/request-review.mdcCursor rule
- .cursor/rules/research-first.mdcCursor rule
- .cursor/rules/reset-baseline.mdcCursor rule
- .cursor/rules/respond-review.mdcCursor rule
- .cursor/rules/run-benchmark.mdcCursor rule
- .cursor/rules/run-evals.mdcCursor rule
- .cursor/rules/run-planning.mdcCursor rule
- The first 60 shown.
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
- Distinctive: line 12
Read the project's current state and give a phase map + next-skill recommendation.
- Very specific: line 26
If CONVENTIONS.md exists at the project root, read it first.
- Distinctive: line 55
If CLAUDE.md exists at the project root, read it for project context (stack, commands, architecture, conventions).
- Very specific: line 59
Read state.yaml vcs.kind (or resolve auto).
- Very specific: line 87
Prefer specs/state.yaml active_flow and handoff.next_skill when present.
- Distinctive: line 112
If something looks wrong:
≈ “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.
Files
<!-- 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-contextconsumes existing specs and docs (fast; does not re-derive).map-codebasebuilds the tech-stack doc from scratch by scanning the codebase. Runmap-codebasewhenspecs/tech-architecture/tech-stack.mddoesn't exist yet; runsurvey-contextwhen 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-contextat invocation;bash scripts/bp-timing.sh end survey-contextbefore 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.yamlFor 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 5For 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:
| Phase | Signals |
| Discover | No requirements/SCOPE_LATEST.yaml yet, or only rough notes |
| Design | SCOPE exists but no release-plan.yaml |
| Plan | release-plan.yaml exists; on main/master branch |
| Initiate | On a feature branch; no code changes yet |
| Execute | state.yaml active_flow: build_epic; epic capsule in progress |
| Verify | Implementation done; run verify-work or run-evals |
| Bug | state.yaml active_flow: fix_bug or open specs/bugs/BUG-*.md |
| Review | All code written; no PR yet |
| Integrate | PR open; tests passing |
| Sustain | Ongoing; 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: Suggestkickoff-branchnext. - If in Initiate phase: Suggest
develop-tddorexecute-planorship-epic. - If in Execute phase: Suggest
ship-epic(resume) ordevelop-tddforactive_story_id. - If in Verify phase: Suggest
verify-work(UAT) orrun-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-*.mdwith no active fix branch - Epic shards missing
verify:on tasks validate-specs-yaml.shfails- Git hash in
state.yamlstale vsgit 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 -->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
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.

