Skip to content
SystematicStructured Engineering Workflows for OpenCode

Using Systematic

View source
Terminal window
npx skills add marcusrbrown/systematic --skill using-systematic
If you were dispatched as a subagent to execute a specific task, skip this skill. If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.

IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.

This is not negotiable. This is not optional. You cannot rationalize your way out of this.

Instruction Priority

Section titled “Instruction Priority”

Systematic skills override default system prompt behavior, but user instructions always take precedence:

  1. User’s explicit instructions (CLAUDE.md, GEMINI.md, AGENTS.md, direct requests) — highest priority
  2. Systematic skills — override default system behavior where they conflict
  3. Default system prompt — lowest priority

If CLAUDE.md, GEMINI.md, or AGENTS.md says “don’t use TDD” and a skill says “always use TDD,” follow the user’s instructions. The user is in control.

How to Access Skills

Section titled “How to Access Skills”

Using Skills

Section titled “Using Skills”

The Rule

Section titled “The Rule”

Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don’t need to use it.

digraph skill_flow {
    "User message received" [shape=doublecircle];
    "About to enter Plan mode?" [shape=doublecircle];
    "Already brainstormed?" [shape=diamond];
    "Invoke brainstorming skill" [shape=box];
    "Might any skill apply?" [shape=diamond];
    "Invoke the relevant skill via the active harness's skill-loading mechanism" [shape=box];
    "Announce: 'Using [skill] to [purpose]'" [shape=box];
    "Has checklist?" [shape=diamond];
    "Create todo per item" [shape=box];
    "Follow skill exactly" [shape=box];
    "Respond (including clarifications)" [shape=doublecircle];


    "About to enter Plan mode?" -> "Already brainstormed?";
    "Already brainstormed?" -> "Invoke brainstorming skill" [label="no"];
    "Already brainstormed?" -> "Might any skill apply?" [label="yes"];
    "Invoke brainstorming skill" -> "Might any skill apply?";


    "User message received" -> "Might any skill apply?";
    "Might any skill apply?" -> "Invoke the relevant skill via the active harness's skill-loading mechanism" [label="yes, even 1%"];
    "Might any skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
    "Invoke the relevant skill via the active harness's skill-loading mechanism" -> "Announce: 'Using [skill] to [purpose]'";
    "Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
    "Has checklist?" -> "Create todo per item" [label="yes"];
    "Has checklist?" -> "Follow skill exactly" [label="no"];
    "Create todo per item" -> "Follow skill exactly";
}

Red Flags

Section titled “Red Flags”

These thoughts mean STOP—you’re rationalizing:

ThoughtReality
”This is just a simple question”Questions are tasks. Check for skills.
”I need more context first”Skill check comes BEFORE clarifying questions.
”Let me explore the codebase first”Skills tell you HOW to explore. Check first.
”I can check git/files quickly”Files lack conversation context. Check for skills.
”Let me gather information first”Skills tell you HOW to gather information.
”This doesn’t need a formal skill”If a skill exists, use it.
”I remember this skill”Skills evolve. Read current version.
”This doesn’t count as a task”Action = task. Check for skills.
”The skill is overkill”Simple things become complex. Use it.
”I’ll just do this one thing first”Check BEFORE doing anything.
”This feels productive”Undisciplined action wastes time. Skills prevent this.
”I know what that means”Knowing the concept != using the skill. Invoke it.

Skill Priority

Section titled “Skill Priority”

When multiple skills could apply, use this order:

  1. Process skills first (brainstorming, debugging) - these determine HOW to approach the task
  2. Implementation skills second (frontend-design, mcp-builder) - these guide execution

“Let’s build X” -> brainstorming first, then implementation skills. “Fix this bug” -> debugging first, then domain-specific skills.

Skill Types

Section titled “Skill Types”

Rigid (TDD, debugging): Follow exactly. Don’t adapt away discipline. The canonical bundled Rigid skill is test-driven-development — load it when implementing any feature or bugfix that requires test-first discipline.

Flexible (patterns): Adapt principles to context.

The skill itself tells you which.

User Instructions

Section titled “User Instructions”

Instructions say WHAT, not HOW. “Add X” or “Fix Y” doesn’t mean skip workflows.

Capability Resolution

Section titled “Capability Resolution”

The four capabilities are subagent delegation, blocking user interaction, task tracking, and skill loading.

The bootstrap inlines the active harness profile naming the exact mechanisms for this session—consult it.

When a mechanism is unavailable, present numbered options in chat and wait for questions, maintain a visible list for task tracking, and dispatch delegation sequentially or do the work inline.

Check the workflow guard availability once per execution unit. If the guard reports unavailable or guard-unavailable, treat it as terminal for that unit: do not retry systematic_workflow_start or systematic_workflow_complete. Use the documented unguarded fallback only when authorized, and report the unavailable state once.

Privacy