mission-brief

Packages phase-plan tasks into self-contained mission briefs for teammates or solo persona runs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill mission-brief-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mission-brief
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/mission-brief
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill mission-brief-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Remote and solo agent-driven teams lose context at handoff: a teammate opening a task in a fresh session does not know what to build, against which contracts, on which branch, or under which rules. This Skill assembles phase-plan tasks into a self-contained mission brief that any agent session can execute cold. ## Core Features & Use Cases - Context Capsule Assembly: Bundles the project one-liner, mission goal, verbatim task cards, owned vs consumed contracts, stack rules, branch names, and sync expectations into one brief. - Team and Solo Modes: Generates one mission file per member matched to TEAM.md strengths, or maps missions to sequenced persona runs with a QUEUE.md for solo operators. - Dependency and Load Checks: Slices missions by track and dependency DAG, marks WAITS-ON lines with mock paths, flags PARALLEL-OK missions, and validates card timeboxes against declared hours at 70% capacity. - Use Case: A lead finishing sprint planning runs this Skill to produce missions/<name>-mission.md files so each teammate's agent session starts with full context and an acceptance checkbox. ## Quick Start Use the mission-brief skill to package the current phase plan into per-member mission briefs under the missions directory.

Frequently Asked Questions about mission-brief

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

FAQPage Schema
How do I create a mission brief for a remote teammate?

Run the mission-brief skill during /missions to slice phase-plan cards by track and dependency, then assemble a context capsule with the goal, task cards, owned and consumed contracts, branch names, and sync expectations into missions/<name>-mission.md.

What should a mission brief include for agent handoff?

A mission brief includes the project one-liner and demo narrative, the mission goal, verbatim task cards, contracts it owns versus consumes, stack rules, branch naming, sync expectations, a definition of victory, and an acceptance checkbox.

Can mission briefs work for a solo developer?

Yes. In solo mode, missions map to persona runs sequenced by the dependency DAG into a queue in missions/QUEUE.md, with PARALLEL-OK missions runnable simultaneously in git worktrees and each mission ending in a PR plus fresh-session review.

How are cross-mission dependencies handled?

Cross-mission dependencies surface as WAITS-ON lines naming the owning mission, and each WAITS-ON must include a mock path so waiting on another track never blocks building.

How does the skill prevent mission overload?

It performs a load check comparing card timeboxes against each member's declared hours in TEAM.md, capping assignments at 70 percent of available capacity.