yansfil

gen-prd

Project-local PRD writer. Use when the user invokes "$gen-prd", asks for a PRD, product requirements document, implementation-ready requirements, or wants to turn intake/clarify output into a human-reviewable requirements contract with major technical structure changes, PRD-level tasks, a compact verification contract, required test modes, human verification, risks, guardrails, and an implementation result report contract.

ho-setup

Project-local PRD pipeline configuration. Use when the user invokes "$ho-setup", asks to enable or change PR delivery mode, configure worktree/secrets sync for implement, configure the agents/ namespace gitignore policy, inspect the current PRD pipeline settings, or diagnose why implement/ship delivery is not working.

implement

Project-local approved-PRD implementation orchestrator. Use when the user invokes "$implement", explicitly asks to execute an approved PRD through the receipt-backed workflow, or wants PRD tasks implemented and proven through one unified verification command. Do not use for ordinary implementation requests that have no approved PRD.

interview-me

Project-local pre-PRD requirements interview. Use when the user invokes "$interview-me", asks to interview an idea, clarify or pressure-test requirements, reduce ambiguity, prepare a PRD source, or wants UX, behavior, scope, technical, verification, risk, operation, and documented-domain decisions captured before writing a PRD. Run low-latency main-agent-led Q&A with raw capture, decision tracking, targeted UX scenario coverage, periodic checkpoint backfill, and a final PRD-ready qa-log.

please

All-in-one PRD pipeline runner. Use when the user invokes "$please", asks to take the current conversation and carry it through to a finished implementation in one shot, wants the gen-prd then implement then ship chain run automatically without approval round-trips, or says things like "그냥 끝까지 해줘", "대화한 대로 구현까지 해줘", "one shot implement this".

remember

Land a lesson as an enforcement asset so the same mistake cannot repeat. Use when the user invokes "$remember", says "remember this", "learn from this", "don't do that again", "배워둬", "기억해둬", "같은 실수 하지마", when a finalize receipt suggests lessons from recorded deviations, or when a painful debugging/rework session just ended and its cause is nameable.

ship

Publish a completed `implement` receipt through GitHub PR delivery. Use when the user invokes "$ship" or explicitly asks to open or update a PR, push a completed PRD implementation, watch CI, or merge an approved green PR through the recorded delivery workflow. Do not use before a complete `implement` receipt exists.

benchmark-implement

Run an approved PRD through the existing receipt-backed implement workflow, analyze its runtime session with a fresh independent evaluator, emit a deterministic process report, and compare it with an earlier run. Use when the user invokes "$benchmark-implement", asks to benchmark the implement skill or harness, rerun a fixed PRD after harness changes, analyze implementation-session efficiency, or compare baseline and candidate harness behavior.

quick

Session-context quick pipeline: contract, implement, verified receipt. Use when the user invokes "$quick", asks to implement something small from the current conversation without the PRD pipeline, or wants the minimal path that still ends in a machine-checked verification PASS. The spec is the conversation compressed into acceptance criteria; verification is the full `sasu gate verify` command (mechanical checks plus an independent diff judge). Do not use when a PRD exists or the user asks for the PRD pipeline.