Context brief

Skill yuri-semenenko/ai-engineering-workspace/codex/skills/context-brief

One engineering workflow across Claude Code, Codex, Copilot, and Gemini CLI. A portable persona canon, process skills, and safety guardrails, kept in sync by design.

Install

npx -y skills add yuri-semenenko/ai-engineering-workspace --skill context-brief

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when preparing a compact handoff, task brief, implementation context, or review packet before a complex change, PR review, debugging session, or agent delegation.

SKILL.md

1.4 KB, as published. Nobody here has run it

Context Brief

Create a bounded brief that lets another pass work from evidence instead of chat history.

Process

State the goal in one or two sentences.
Capture constraints: scope, non-goals, deadlines, risky areas, and user preferences that affect execution.
List relevant files, commands, tickets, PRs, docs, and external references with why each matters.
Summarize observed facts separately from assumptions.
Identify open questions that block safe implementation or review.
Recommend the next action: implement, investigate, review, ask the user, or stop.

Output

Use this shape unless the user asks for another format:

## Goal
<what needs to happen>

## Constraints
- <scope, non-goals, verification, timing, ownership>

## Evidence
- `<path or command>` - <why it matters>

## Facts
- <verified fact>

## Assumptions
- <assumption and why it is acceptable or risky>

## Open Questions
- <question or "None">

## Recommended Next Step
<one concrete next action>