fankeel

Plugin fankeel from marketplace fankeel in FanFantom9452/FanKeel. Commands read from the repo's manifest — 10 days ago.

Skills (16)

• fankeel-ask

  Interrupt the stage you are in and put one question to a stronger model — a one-shot judge whose answer is filed verbatim and then acted on. Use for /fankeel-ask, "問判官", "叫 fable", "這題我們解不開", or when a mid-stage question is worth a model above the one running the session.

• fankeel-audit

  Audit documentation against the code it describes — dead references, pages that stopped being true, two pages describing one thing, plans whose work has landed, orphans. Use for /fankeel-audit, "check the docs", "what is out of date", "文件審查", before a release, or when two documents disagree.

• fankeel-build

  The build stage — run a plan's tasks, or a design's file table where there is no plan, in a loop that does not stop to ask, keeping its place in a ledger and reviewing each task as it lands. Use for the build stage of a fankeel task, implementing an approved plan, resuming build work after a compact

• fankeel-design

  The design stage — one approach with its trade-offs, a success criterion that can fail, and a check against the project map before anything is built. Use for the design stage of a fankeel task, choosing between approaches, writing a spec, or when an approach needs approving before implementation.

• fankeel-explain

  Say it so it is understood on first reading — the one sentence first, unknowns left unknown, contrast only where evidence has one, a report as a path, a status sync in six fields, and a check before sending. Use for a presentation, a report, a project status sync or init, sorting out a line of thoug

• fankeel-init

  First-use onboarding for a project fankeel has not organised — its docs tree, raw data, TODO, directory tree, CLAUDE.md, memory and a sensitive-word list — one question at a time until the onboarding checks pass. Use when `task.js start` prints an `onboard:` line, or for /fankeel-init.

• fankeel-land

  The land stage — a green suite, the documents closed, the map rewritten, and the integration decision left to the user. Use for the land stage of a fankeel task, finishing a development branch, deciding between merge and PR, or cleaning up a worktree when work is complete.

• fankeel-phone

  Hand this session to the phone — when this turn ends the session waits for the next message typed on the station's phone page (/m). Use for /fankeel-phone, "交給手機", or before walking away from a session you want to keep talking to.

• fankeel-plan

  The plan stage — decompose an approved design into tasks someone with no context could execute, with constraints generated from the project rather than remembered. Use for the plan stage of a fankeel task, writing an implementation plan, or breaking a spec into tasks before any code is written.

• fankeel-retro-all

  Review every exported session bundle for problems that recur across tasks — this machine's and other users' — and propose skill, agent or stage-rule edits only for what recurs. Use for /fankeel-retro-all, "跑全部 retro", "回顧所有 session", or after importing a retro ZIP another user sent back.

• fankeel-station

  Reopen the station by hand — every fankeel session on this machine on one page, served live. `/fankeel` already starts it and names its url on the block's station line, so this is for a station that was stopped or a tab that was closed. Use for /fankeel-station, "開站", or when the station has to be a

• fankeel-survey

  The survey stage — read the project's own map before reading its code, classify the work, and report what is already here. Use for the survey stage of a fankeel task, "what is already here", starting work in an unfamiliar repository, or when a task needs classifying as spike, bounded or architectura

• fankeel-upgrade

  Bring a project up to what the installed fankeel expects — what changed since the last upgrade, which migrations are pending, and each one asked about before it runs. Use for /fankeel-upgrade, "升級 fankeel", or after updating the plugin.

• fankeel-verify

  The verify stage — evidence before claims, requirements checked line by line, and the documents this change just made false. Use for the verify stage of a fankeel task, before claiming work is complete or passing, before a commit or PR, or when checking whether a change broke the documentation descr

• fankeel-weekly

  The weekly report for the professors — pick a date range and the repositories, collect fankeel's records, session records and git history for it, write what was done as a list the user confirms, then render one self-contained HTML page archived under the config dir. Use for /fankeel-weekly, "週報", "寫

• fankeel

  Task registry and development discipline for long-running projects. Use for /fankeel, starting or pausing a task, asking what this or another session is working on, moving to the next stage, or the station — "show all sessions", "which sessions are still open", "clean up old sessions", "監控站". Runs a

Subagents (15)

• fankeel-brain

  A stage agent — runs one whole stage in a clean context when the profile's stage.agents names that stage, dispatches fankeel-reader and fankeel-reviewer for the reading and the reviewing, on a build stage its fixer and implementers, on a verify stage its verifier, fixer and mutator, on audit a mover

• fankeel-fixer

  Surgical fixer for a reference-page correction or a one-line code fix that needs no test run — verify's and audit's dead references and false sentences, and the small code fixes a reviewer already named. Refuses a fix that touches 3 or more files. Cannot call Bash, PowerShell or NotebookEdit.

• fankeel-implementer

  Build's implementer — builds one plan task, test first, in the least code that does the job correctly, reusing what the repository already has and commenting only what the code cannot say. Returns the status, paths and test lines the brief footer asks for. Sent with the model the task's Dispatch lin

• fankeel-init-scout

  Read-only scout for fankeel-init — runs the onboarding checks and returns a status row for every onboarding step and drafts for the open ones — what each tree row is for, which bucket an unfiled page belongs in, which directories hold raw data, which pages read out of date, and where workspace and r

• fankeel-judge

  One-shot judgement for a question the session would otherwise put to the user mid-stage — a design clarification, a class, a plan split, a build choice. Lists what it must check, sends every read to a fankeel-reader in one response, spot-checks one line per reader, and answers once in a fixed shape

• fankeel-mockup

  Draws the design stage's mockup — one HTML page built from the project's own stylesheets and rendered DOM, every changed block carrying data-block — and, in a tuning loop, rewrites only the one block a request names. Reads fankeel's design guide, then loads every design skill the prompt names, befor

• fankeel-mover

  Audit's and land's file mover — runs the git mv, merge or deletion of named files it is given, one action at a time, and returns each command with its result. Never changes a file's content. Cannot call Edit, Write or NotebookEdit.

• fankeel-mutator

  Verify's mutation runner — applies the one mutation it is given at a path:line, runs the one node --test command it is given, restores the file, and returns the pass and fail lines before and after with git diff --stat as proof of the restore. Refuses more than one mutation or a command that is not

• fankeel-reader

  Read-only reader for a stage's reading fan-outs — reads files, runs git and the plugin's scripts, and returns only the lines that decide the question it was sent with. Cannot call Edit, Write or NotebookEdit.

• fankeel-render-reviewer

  Rendering reviewer for build's frontend tasks and verify — shoots every role and page `.fankeel/render.json` declares with the plugin's render script, shoots the approved mockup at the same size, and returns a data-block by role matrix and a disposition of recapture, fix or ship. Cannot call Edit, W

• fankeel-retro

  Land's retro — reads one session's transcript through `scripts/conversation.js` and proposes skill or CLAUDE.md edits as a unified diff, one evidence line per hunk, for the user to approve. Sent after every 匯出並回顧 the user picks at land. Refuses without a session id. Cannot call Edit, Write or Notebo

• fankeel-reviewer

  Read-only reviewer for the plan review, build's per-task review, verify's adversary and audit's code half — reads a diff, a brief, an evidence table or the whole tree against what it was supposed to prove, and returns only what it defeats and, when asked, what could be cut. Cannot call Edit, Write o

• fankeel-slimmer

  Slims what is read every turn — CLAUDE.md files and MEMORY.md with the memory files it lists. Runs `scripts/input-check.js`, proposes cuts as a diff for the user to approve, and never deletes a memory file without approval. Cannot call Edit, Write or NotebookEdit.

• fankeel-verifier

  Writes one task's evidence rows to a file and returns the path — verify's per-task verifier. Runs tests and read-only git; writes nothing but the evidence file it was given a path for.

• fankeel-writer

  Writes one human-facing docs page — a page under the guide directory or README.md — in full sentences, every section carrying what it does, why, and an example to copy, from facts it can point at by path:line. Refuses any other target, more than one page, or no page path. Cannot dispatch a subagent

Hooks (20)

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/carry.js"

• UserPromptSubmit

  node "${CLAUDE_PLUGIN_ROOT}/hooks/inject.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/resume.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/touch.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/gate-write.js"

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/budget.js"

• SubagentStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/brief.js"

• SubagentStart

  node "${CLAUDE_PLUGIN_ROOT}/hooks/agent-end.js"

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/agent-end.js"

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/stop.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/guard.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/gate.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/guard.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/guard.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/title.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/dispatch-gate.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/relay-cap.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/wrap-up.js"

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/budget.js"

• SessionEnd

  node "${CLAUDE_PLUGIN_ROOT}/hooks/leave.js"

Similar plugins