Engineering skills: SQL, clean architecture, clean code, DDD, database optimization, chaos engineering, Spring Boot, Kotlin, TDD, testing, bug diagnosis, security audit, architecture review, deprecation & migration, SRE, performance profiling & optimization, incident response, documentation strategy, like-my-code (a repo's style as harness conventions, each rule with evidence and a cited source). ADR drafting moved to write:plans (ADR format); diagram moved to write:diagram.
36 skills · hooks
A sibling of graph for requests too big for one pass: a TaskManager MCP (teams) sizes the request; size L is planned into a PRD and user stories, split into packages that each run the full harness in their own worktree, integrated, QA'd and gated by a background daemon; size S is handed to the development harness. Entry skills teams:orchestrate/develop/document/plan/qa/sprint, board and ticket views (tm_board, teams:board). Runs are kept under .teams_output/ and ~/.harness/tasks/. Zero runtime dependencies beyond Node 18+.
15 skills · 1 MCP server · hooks
Portfolio and career skills: manage (the portfolio deck as one workflow — material, skeleton, feedback, deck, versions), material (collect handed material), fit (JD or company type), portfolio feedback, rewriting and JD tailoring, pattern analysis, mock interview, interview plan, job-application-workflow (through a 자기소개서 step via write:writer-verification), deck-builder (reference template.pptx + deck.mdx → pptx; recolors a pptx to a brand palette), resume-builder (resume-deck.mdx → the user's own .docx, PDF, page fit, final AI-trace check), and render-review (page-by-page review of a rendered deck or resume).
12 skills · hooks
Thinking quality skills: assumption extraction, bias auditing (v2 — context probe, per-bias remedies, calibration check), fallacy detection, mental models, epistemic reasoning, tradeoff articulation, question upgrading, and second-order thinking.
10 skills · hooks
Writing skills: plans (gate-ready implementation plans and ticket breakdowns with production-time gap/ambiguity checks + per-step pass bars; technical blog posts; SBI feedback), prd (PRDs, design docs, RFCs and proposals co-written section by section with reader testing), adr (ADRs and fixed-template design reviews), requirements (a requirement or 기획서 split into actors, rules, open questions with defaults, and items with Given/When/Then criteria),spec (a settled conversation synthesised into a spec, open points marked, no re-interview), skill writing, and writer verification (v2 — five passes incl. a humanizer for machine tells, draft loop that rewrites until 🔴🟡 = 0, PR descriptions from a diff as first-class input), and tech-book (performance-based book arc, cumulative examples, transfer practice, six required teaching elements within a chapter length budget, staged review loops with defined severities, lab-running fact checks, pinned chapter end states and a cap closure pass, and PDF in bundled NanumGothic), diagram (checked self-contained SVG + PNG figures: page layout, B-tree, lock timeline, ER, chart, architecture, sequence; moved from develop). Knowledge-base, graph, RAG, and query skills moved to the knowledge plugin.
10 skills · hooks
Thinking and ideation skills: mentor (any-field mentoring — takes a position, tests yours, hands over the judgment rule), brainstorming (≥3 options before judgment, kill-criteria convergence, hands off to write:plans), grill (a held plan interrogated: repo read first, one numbered round with recommended answers), devils-advocate (steel-man first, core vulnerability + reversibility), redefine-problem, back-to-basics, untangle-thoughts, and negotiate (counsel on your side).
8 skills · hooks