skills-workflows

# Skills Workflows

Design skill systems that chain together with artifact-based state passing.

## Steps

1. Load the `outfitter:skills-dev` skill for base skill authoring
2. Apply workflow patterns from this skill
3. If Claude-specific features needed, load the `outfitter:claude-skills` skill

<when_to_use>

- Building multi-skill pipelines (triage → plan → implement → review)
- Designing state handoff between workflow steps
- Creating deterministic preprocessing with `!command` syntax
- Setting up shared conventions (artifacts/, context.md)
- Choosing fork vs inherit for workflow isolation

NOT for: single standalone skills, one-off commands, simple patterns

</when_to_use>

## Shared Conventions

Every workflow system benefits from standard file locations:

```text
.claude/
  skills/
    _shared/
      context.md       # Living summary of current task + decisions
      constraints.md   # Non-negotiables (security, style, perf budgets)
    triage/SKILL.md
    plan/SKILL.md
    implement/SKILL.md
    review/SKILL.md
artifacts/
  triage.md           # Output of /triage
  plan.md             # Output of /plan
  test-report.md      # Output of /test
  review-notes.md     # Output of /review
scripts/
  run-tests.sh
  security-check.sh
```

| File | Purpose | Updated By |
|------|---------|------------|
| `context.md` | Task state, decisions made, current focus | Each skill as work progresses |
| `constraints.md` | Project invariants, security rules, style guide | Setup once, rarely changed |
| `artifacts/{step}.md` | Step outputs, consumed by next step | The skill that completes that step |

## State Passing Discipline

Each skill reads from previous artifacts and writes its own:

```text
/triage → writes artifacts/triage.md
    ↓
/plan reads artifacts/triage.md → writes artifacts/plan.md
    ↓
/implement reads artifacts/plan.md → updates context.md
    ↓
/test reads artifacts/plan.md → writes artifacts/test-report.md
    ↓
/review reads all → writes artifacts/review-