When a user requests work that involves any of:

Start with /team-brief by invoking it via the Skill tool: Skill({ skill: "team-brief" }).

Follow the workflow chain: brief -> design -> review -> plan -> build -> qa -> ship. Each step has an explicit approval gate. Do not skip ahead.

What counts as trivial (skip the workflow)

Single-file bug fixes, config changes, typos, simple queries, research, conversation.

Common mistakes

Writing a brief-like document yourself instead of invoking /team-brief. The skill has specific file paths (.context/specs/<feature>/), a Q&A process, and output templates that only load when invoked.
Chatting through requirements and jumping to implementation. That skips the brief and design.
Creating plan or design files ad-hoc. The /team-design and skills produce those.

When a user requests work that involves any of:

Start with /team-brief by invoking it via the Skill tool: Skill({ skill: "team-brief" }).

Follow the workflow chain: brief -> design -> review -> plan -> build -> qa -> ship. Each step has an explicit approval gate. Do not skip ahead.

Single-file bug fixes, config changes, typos, simple queries, research, conversation.

Writing a brief-like document yourself instead of invoking /team-brief. The skill has specific file paths (.context/specs/<feature>/), a Q&A process, and output templates that only load when invoked.
Chatting through requirements and jumping to implementation. That skips the brief and design.
Creating plan or design files ad-hoc. The /team-design and skills produce those.