Step 6 — Building workflows

Skills + MCP + Hooks together turn repeated work into one command. The real value is here.

Example — a feature workflow

.claude/skills/feature.md

---
name: feature
description: Standard new-feature flow
---

7 steps:

1. Read CLAUDE.md and docs/agent/{service}/rules.md
2. Grep for existing patterns
3. Implement (TDD if possible)
4. tsc --noEmit + lint + test
5. Update affected docs/*
6. Grep for AI-credit patterns
7. Korean one-line `[type]` commit (push is the user's)

Larger — /cycle

Orchestrates several skills:

---
name: cycle
description: Full work cycle (understand → plan → modify → verify → refine → docs → commit)
---

1. Understand — restate user intent in one line
2. Plan — list candidate files
3. Modify — Edit/Write
4. Verify — call `/check`
5. Refine — call `simplify`
6. Docs — update by mapping table
7. Commit — call `/commit`

Hook + Skill combo

{
  "hooks": {
    "Stop": [{ "type": "command", "command": "git status --short" }]
  }
}

End-of-session reminder of uncommitted changes.

Five tips

1. Skill it only if you do it monthly+
2. One command = one responsibility
3. Always summarize what was done
4. Halt clearly on failure
5. Log so you can audit later

Try it

Pick a daily routine of yours (e.g., "delete current branch and return to main, fetch latest") and turn it into a skill.

Course done

AI tooling moves weekly — bookmark agent-tooling notes. Continue with devops-cloud or backend-with-spring.