context-investigator

Aggregate project context from HANDOFF.md, README, ADRs, and repository structure.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill context-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-investigator
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/context-investigator
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill context-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the gathering of project context to enable accurate task decomposition for sprint planning. It reads HANDOFF.md, project context briefs, glossary, README, recent commits, and the repository structure to surface domain knowledge and patterns.

Core Features & Use Cases

  • Reads HANDOFF.md to capture recent activity, open questions, important decisions, and next priorities.
  • Scans project context briefs and glossary to map domain terms, stakeholders, goals, and technology stack.
  • Analyzes the root README for project description, setup hints, and architecture overview.
  • Aggregates architectural decisions/ADRs to inform design constraints and trade-offs.
  • Produces a structured context snapshot to guide downstream sprint-decomposition agents.

Quick Start

Run the context-investigator at sprint start to generate a context snapshot for the decomposer.

Frequently Asked Questions about context-investigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather project context for sprint planning and task decomposition?

To gather project context for sprint planning, the context-investigator reads HANDOFF.md, glossary, README, ADRs, and repository structure to produce a structured context snapshot for downstream sprint-decomposition agents.

What is a HANDOFF.md file used for in a sprint workflow?

A HANDOFF.md file is used to capture recent activity, open questions, important decisions, and next priorities, which the context-investigator reads to maintain continuity and inform sprint planning.

How do I map domain terms and technology stack from repository documentation?

To map domain terms and technology stack from repository documentation, scan project context briefs, glossary, and the root README to surface domain knowledge, stakeholders, goals, and architectural patterns.

When do I need to analyze ADRs and project structure for sprint planning?

You need to analyze ADRs and project structure at sprint start to infer design constraints, trade-offs, and domain context, ensuring accurate task decomposition by the sprint orchestrator.

Does the context-investigator require specific dependencies or components to run?

No, the context-investigator has zero dependencies and requires no external components, requiring only standard repository files like HANDOFF.md, README, ADRs, and glossary to generate a context snapshot.

What are the limitations of using repository files for automated context aggregation?

The limitation of automated context aggregation is its reliance on up-to-date repository documentation; missing or outdated HANDOFF.md, glossary, or ADR files will reduce the accuracy of the context snapshot.