project-briefing

Gathers sub-project context and emits a structured briefing block for downstream agents.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/jakestrouse00/opencode-toolkit --skill project-briefing-jakestrouse00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-briefing
Source: https://github.com/jakestrouse00/opencode-toolkit/tree/main/skills/project-briefing
Command: npx skills add https://github.com/jakestrouse00/opencode-toolkit --skill project-briefing-jakestrouse00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When handing a complex task to a downstream orchestrator agent in a multi-project workspace, that agent lacks the project context it needs. This Skill gathers the relevant documentation, structure, tech stack, and open plans for one sub-project and packages them into a paste-ready briefing block. ## Core Features & Use Cases - Interactive scoping: Asks which sub-project to brief on, which information dimensions to include (overview, structure, tech stack, architecture, active work), and what the intended goal is, skipping questions already answered in the trigger message. - Read-only context gathering: Reads AGENTS.md, READMEs, manifests, directory trees, and plan/note files filtered by Project header, with batched concurrent reads and graceful degradation to placeholder text when sources are missing. - Goal-oriented synthesis: Emits a markdown briefing block ending with suggested focus areas tailored to the goal (new features, refinements, bug hunt, or architecture review), with file:line anchors. - Use Case: You want the multi-agent discussion orchestrator to brainstorm features for your CLI tool. Run the briefing, pick the tool and the relevant dimensions, then paste the emitted block into the orchestrator session. ## Quick Start Ask the assistant to give you a project briefing for one of the sub-projects in this workspace so you can hand the context to the orchestrator agent.

Frequently Asked Questions about project-briefing

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

FAQPage Schema
How do I give an orchestrator agent context about a sub-project?

Run the project-briefing skill, pick the sub-project and the information dimensions you need, and state the goal. It emits a structured markdown briefing block in chat that you paste directly into the downstream agent session.

What information does a project briefing include?

Up to five dimensions: overview from README/AGENTS.md, a top-two-level directory tree, tech stack from manifests like pyproject.toml or package.json, architecture and conventions from AGENTS.md, and open plans or notes matching the sub-project's Project header.

Does project-briefing work in a single-app repository?

No. It only applies when the workspace's AGENTS.md documents a sub-project layout with multiple projects under the repo root. In a single-app repo it reports that there is nothing to brief on and stops.

Does the briefing skill modify files or run tests?

No. It is strictly read-only: it never edits, writes, commits, runs tests or linters, or starts a discussion. It may report the test commands documented in AGENTS.md but never executes them.

What happens if a sub-project has no README or manifest?

Each dimension degrades independently. Missing sources produce an explicit placeholder such as "(none found)" for that section rather than failing the whole briefing, and the focus-areas section is always emitted.