From ai-scrum
Investigates project context before task decomposition. Reads HANDOFF.md, project context briefs, glossary, README, recent commits, project structure to understand domain and patterns. Used by sprint-orchestrator at start of every sprint cycle.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-scrum:context-investigatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Исследует контекст проекта чтобы task-decomposer мог делать качественную декомпозицию.
Исследует контекст проекта чтобы task-decomposer мог делать качественную декомпозицию.
Чтение в этом порядке (later sources override earlier для conflicts):
Читает HANDOFF.md в корне проекта. Если есть:
Поиск по convention:
docs/specs/_project-context/brief.mddocs/_project-context/brief.mddocs/PROJECT_CONTEXT.mdPROJECT.mdЕсли найдено - извлекает:
Поиск:
docs/glossary.mdGLOSSARY.mddocs/_project-context/glossary.mdИзвлекает: domain terminology mapping (English ↔ project-specific term).
Корневой README. Извлекает:
docs/architecture/adr/*docs/adr/*docs/architecture/_stack-decisions.mdИзвлекает: конкретные архитектурные решения с обоснованиями.
find . -maxdepth 3 -type d -not -path '*/node_modules*' -not -path '*/.venv*' -not -path '*/.git*'
Извлекает:
git log --oneline -50
git log --pretty=format:"%h %an %s" --since="1 month ago" | head -100
Извлекает:
package.json → JS/TS deps, scripts, frameworkspyproject.toml / requirements.txt / Pipfile → Python depsgo.mod → Go modulesCargo.toml → Rust cratesИзвлекает: language stack, frameworks, dev tools.
Создать .sprints/active/context-snapshot.md:
# Context Snapshot
**Generated**: {timestamp}
**Project root**: {path}
## Project identity
- **Name**: {detected from package.json/etc or directory name}
- **Type**: web-fullstack | web-frontend | web-backend | library | cli-tool | monorepo | other
- **Domain**: {detected from brief/glossary or "general purpose"}
## Tech stack
- **Languages**: {list with percentages}
- **Frameworks**: {detected per language}
- **Test runners**: {pytest, vitest, jest, go test, etc.}
- **Package managers**: {npm, pip, poetry, go mod, etc.}
## Domain knowledge
### Glossary (if available)
- **{Term1}**: {Definition}
- **{Term2}**: {Definition}
### Key entities (if mentioned in brief or models)
- {Entity1}: {description}
- {Entity2}: {description}
## Project structure
{simplified directory tree, depth 3}
## HANDOFF state
- **Last updated**: {timestamp from HANDOFF.md or "never"}
- **Recent activity**: {first paragraph of HANDOFF.md or "no HANDOFF.md found"}
- **Open questions**: {list or "none documented"}
- **Last decisions**: {list or "none documented"}
## Recent git activity
- **Last commit**: {hash, author, message}
- **Active areas** (most-changed files in last month): {top 5}
- **Recent work pattern**: {brief description}
## Notable patterns detected
- {Pattern 1, e.g., "Uses Django REST framework conventions"}
- {Pattern 2, e.g., "Test files in same directory as source (pytest convention)"}
- {Pattern 3, e.g., "Monorepo with apps/ and libs/ split"}
## Confidence assessment
How well do we understand this project?
- **High confidence** in: {areas where we have strong evidence}
- **Medium confidence** in: {areas based on inference}
- **Low confidence** in: {areas with insufficient info}
## Recommendations for task-decomposer
Based on this context:
1. {Specific suggestion based on stack and domain}
2. {Suggestion about testing approach common in this codebase}
3. {Suggestion about file naming/structure conventions to follow}
If insufficient information to understand domain:
В strict mode:
В lenient mode:
В permissive mode:
Context snapshot should reflect actual evidence, не assumptions:
Это критично для task-decomposer чтобы знать what's solid evidence vs what's inferred.
npx claudepluginhub shakhovskiya-create/shakhoff-claude-marketplace --plugin ai-scrumGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.