← all publishers

hoetaek

@hoetaek source repo

Report this profile Claim this profile

• 33 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Land · hoetaek bundle

   Use after wt work is reviewed or intentionally discarded, or when the user asks for a wt retrospective: respect workflow policy, pass workflow-linked tasks when needed, merge or prove discard, clean with `wt done`, and record retrospective lessons, timing evidence, action candidates, and harness tuning.
   0
   installs
2. ▌
   Ready · hoetaek bundle

   Use before work to verify prepared context is executable as wt development work, slice it, author TaskDocument bodies, choose execution shape and workflow policy, and hand off an exact launch target. For vague work that still needs thinking, route to leaf-work and stop.
   0
   installs
3. ▌
   Config · hoetaek bundle

   Use to inspect the current project and recommend an ideal wt config: ownership, active sections, omitted sections, commands, env templates, providers, workspace, workflow policy, profiles, and validation.
   0
   installs
4. ▌
   Variants · hoetaek bundle

   Use when exploring multiple implementation variants for one wt task by preparing profile-specific matrix workflow runs with distinct workflow prompts, then comparing the resulting PRs before choosing what to land.
   0
   installs
5. ▌
   Ego · hoetaek bundle

   Critic's verdict on finished work — genuinely remarkable, or merely competent and forgettable? Names safe filler, recognizes real brilliance. Not for whether it's finished (→ ramsay) or pushing it further (→ fletcher); Ego judges and stops. Profane only on request.
   0
   installs
6. ▌
   Help · hoetaek

   Quick-reference card for LEAF phases, skills, CLI commands, and update flow. One-shot display, not a persistent mode. Trigger: /leaf:help, $leaf:help, "leaf help", "LEAF commands", "how do I use leaf".
   0
   installs
7. ▌
   Soul · hoetaek bundle

   Use when LEAF work needs the agent's soul: plain explanation, reporting, fact-vs-assumption separation, user-language prose, review handoff, or artifact display.
   0
   installs
8. ▌
   Tend · hoetaek bundle

   Use to keep pressed leaf documents true to current code — sweep the pressed knowledge graph and reconcile drift. Trigger on `leaf tend`, "pressed 문서 최신화", "tend the leaves", "leaf graph 결과가 코드랑 맞는지", "인용 문서가 옛날 거 아닌지", "press된 문서 점검", "knowledge graph 정합성". Reads pressed nodes via `leaf graph`, verifies each claim against the repo, and proposes 🟢keep / 🟡correction-banner / 🔴supersede — never rewriting the frozen pressed body, never falling without user confirmation. Do not use for prose flow cleanup (→ `polish`), first-time pressing (→ `press`), human review handoff (→ `review`), editing gate source documents, or reconciling fallen items.
   0
   installs
9. ▌
   Work · hoetaek bundle

   Use to carry a LEAF sprout after Learn from ③ Example through a shipped result: validate one cheap instance against criteria, design the generator, run the critic, slice the task graph, draft or execute, and review. Use for documents, essays, articles, memos, research papers, proposals, reports, specs, study notes, presentations, prototypes, code, or mixed deliverables in a repo-local `.leaf/` workspace. Enter after ① Intent and ② Unknowns & Context pass in `learn`. Trigger on criteria, 와이어프레임, 설계, task graph, 작업 쪼개기, 초안 작성, 실행, 리뷰, or 검토 절차. For vague, early, or idea-stage work, use `learn` first.
   0
   installs
10. ▌
    Jobs · hoetaek bundle

    Product-taste review of features and flows — does this deserve to exist, and is the experience ruthlessly simple? Hunts feature bloat and choices dumped on the user. Not for visual craft (→ rams) or whether finished work is remarkable (→ ego). Profane only on request.
    0
    installs
11. ▌
    Rams · hoetaek bundle

    Design review against "less, but better" — visual pollution, decoration, dishonest UI, anything removable without loss. UI and components only. Not for product-existence decisions (→ jobs) or prose (→ orwell). Profane only on request.
    0
    installs
12. ▌
    Theo · hoetaek bundle

    Security review of code touching input, auth, crypto, privileges, or network — attack surface, default-deny, least privilege, cut corners. Not for general engineering (→ torvalds) or production-readiness (→ ramsay). Profane only on request.
    0
    installs
13. ▌
    Learn · hoetaek bundle

    Capture or resume a LEAF sprout for explicit learning, durable records, or structured discovery of core unresolved decisions. Route ordinary clear tasks through using-leaf first.
    0
    installs
14. ▌
    Press · hoetaek bundle

    Use when a reference-worthy leaf should be pressed into a citable digest. Trigger on `leaf press`, "press this leaf", "make this leaf citable", "인용용으로 눌러줘", or "write the press abstract". Writes `pressed.md` and a `## Press Abstract` in `00-status.md` without touching source truth. The keep / press / fall decision and the fall and keep actions live in `../using-leaf/references/lifecycle.md` ("Ending a leaf"), not here. Do not use for gate document cleanup or producing the artifact itself.
    0
    installs
15. ▌
    Split · hoetaek

    Use when deciding how to split one piece of work into separate leaves — whether to split at all, along which grain, and how the pieces stay linked. Trigger on `leaf split`, "split this", "should I split", "쪼갤까", "어느 결로 쪼개", "한 작업을 나눈다", "decompose this", or a bundled sprout that may hold independent cores. This first increment carries the judgment framework; the execution (parent fall, child new, link wiring) is a later increment.
    0
    installs
16. ▌
    Pauli · hoetaek bundle

    Falsifiability review of a claim, metric, or rationale — could it even be wrong? Hunts unfalsifiable claims and success criteria with no fail condition. Not for whether an idea is understood (→ feynman) or incident diagnosis (→ sherlock). Profane only on request.
    0
    installs
17. ▌
    Polish · hoetaek bundle

    Use at each phase boundary (and before user review or gate close) to make the cumulative LEAF document — all phases so far read as one connected report — read simply and flow naturally, not as draft notes. Preserve source truth while removing stale options, process chatter, duplicate reasoning, status drift, or doctor-reported legacy layout/status fields. Do not use to create the artifact, decide press/fall close-out, or maintain execution artifacts.
    0
    installs
18. ▌
    Orwell · hoetaek bundle

    Prose review of docs, PR text, commits, comments, copy — dead metaphors, passive voice that hides the actor, jargon, euphemism. Not for whether the ideas are sound (→ feynman/pauli); Orwell judges only the writing. Profane only on request.
    0
    installs
19. ▌
    Ramsay · hoetaek bundle

    Production-readiness review of work claimed done — unhandled errors, missing edge cases, absent tests/migrations/rollback, "works on my machine." Not for security (→ theo), code craft (→ torvalds), or whether it's excellent (→ ego/fletcher). Profane only on request.
    0
    installs
20. ▌
    Install · hoetaek bundle

    Use when the user invokes $leaf:install, asks to install or update the leaf CLI, or LEAF work is blocked because leaf is not on PATH.
    0
    installs
21. ▌
    Profile · hoetaek bundle

    Use when reading, creating, or updating LEAF profiles — the machine-global `~/.config/leaf/profile.md` and the repo-local `.leaf/PROFILE.md`: user language, recurring requirements, agent mistakes, wrong-answer notes, and cross-leaf facts. Read the merged view with `leaf profile`.
    0
    installs
22. ▌
    Sidecar · hoetaek

    Use when the user invokes /leaf:sidecar or $leaf:sidecar, or asks to create, refresh, document, or re-verify a leaf SRP "single responsibility" sidecar contract for a code artifact; also when a `srp_sidecar_stale` doctor warning appears, when someone is hand-writing a `*.leaf.toml`, or when a load-bearing file's responsibility risks being copied or broadened.
    0
    installs
23. ▌
    Council · hoetaek bundle

    Convene the relevant review personas to review one scope, each through its own lens, then a chair synthesizes one ranked verdict. For multi-angle review of a diff, PR, design, doc, or plan. Triggers on "angry council", "angry 패널로 리뷰", "분노 패널". Spawns subagents only when asked; profane only on request.
    0
    installs
24. ▌
    Feynman · hoetaek bundle

    First-principles review of explanations, plans, and claims — actually understood, or cargo-culted? Hunts hand-waving, borrowed authority, jargon hiding empty thought. Not for falsifiability (→ pauli) or incident diagnosis (→ sherlock). Profane only on request.
    0
    installs
25. ▌
    Dijkstra · hoetaek bundle

    Correctness-rigor review of algorithms, state machines, and concurrency — is the code argued correct, or just observed to pass? Hunts missing invariants, unhandled states, accidental complexity. Not for general code quality (→ torvalds) or security (→ theo). Profane only on request.
    0
    installs
26. ▌
    Fletcher · hoetaek bundle

    Mentor review that refuses "good enough" and pushes work to the standard it could reach — the gap between adequate and your best. Attacks the work's standard, never the person. Not for judging remarkable-vs-competent (→ ego) or shippability (→ ramsay). Profane only on request.
    0
    installs
27. ▌
    Sherlock · hoetaek bundle

    Debugging review — does the diagnosis follow from evidence, or is it a guess? Hunts theories formed before data, ignored clues, symptom-only fixes. Not for claim-understanding (→ feynman) or falsifiability (→ pauli). Profane only on request.
    0
    installs
28. ▌
    Torvalds · hoetaek bundle

    Blunt maintainer code review of a diff, PR, branch, or repo — correctness, contracts, data loss, tangled ownership, complexity, weak tests, and the one issue to fix first. Not for security (→ theo), correctness proofs (→ dijkstra), or readiness (→ ramsay). Profane only on request.
    0
    installs
29. ▌
    Autopilot · hoetaek bundle

    Use after a LEAF sprout's why / what / wireframe triple has been explicitly reviewed by the user and the user wants the remaining LEAF lifecycle to proceed automatically. Trigger on "$leaf:autopilot", "LEAF autopilot", "triple is approved, continue automatically", "run the rest of LEAF without asking", or "after this lock, handle the rest". Do not use for execution-ready direct work, unclear intent, destructive/external/credential/cost/security/privacy-sensitive work without explicit pre-authorization, or when the user wants normal per-gate approval.
    0
    installs
30. ▌
    Using Leaf · hoetaek bundle

    Route explicit LEAF work or work needing structured discovery and design; keep clear ordinary tasks direct. Injected at session start.
    0
    installs
31. ▌
    Using Angry · hoetaek bundle

    Use when starting Angry Review work or when the user invokes `$angry`, asks which angry review persona to use, requests an angry review/council/panel, or needs routing among council, single-axis personas, and review/fix loops.
    0
    installs
32. ▌
    Loop Council · hoetaek bundle

    Bounded review/fix loop using council as the engine — convene the panel, fix the chair's top verdict, verify, repeat within budget (default 2). Stops on cross-axis tradeoffs needing a human. Triggers: council loop, loop-council, panel review loop.
    0
    installs
33. ▌
    Loop Torvalds · hoetaek bundle

    Bounded review/fix loop using torvalds as the engine — find the highest-priority issue, fix it, verify, repeat within budget. For a diff, PR, branch, or repo. Triggers: torvalds loop, loop-torvalds, maintainer review loop.
    0
    installs