hani-q
UserA personal stack of agent skills for reviewable planning, disciplined execution, and durable engineering lessons.
Categories
Indexed Skills (23)
qstack-plan-close
Close an executed plan by recording its outcome against the plan and the execution board.
qstack-plan-to-html
Render a Markdown plan as a reviewable QStack HLD/LLD HTML document, resolve its material open questions, and break it into the cards of its execution board. Also adds a board to a plan that already has HTML and no board.
qstack
List every skill installed from QStack and from the optional collections QStack installs (Matt Pocock's skills, human-review) as a table with a one-line description each, then recommend the next skill to run from the conversation so far and the plan folder on disk. Use when invoked as /qstack or when asked which QStack commands exist.
qstack-blast-radius
Assess what a proposed or recent change could break beyond its direct diff, identify the critical safety fact, and prove it with real code or mark it unproven. Use for blast-radius analysis, "what could this break?", or a small change whose downstream effects are uncertain.
qstack-how
Explain how a subsystem works by tracing its real runtime flow, ownership, boundaries, and files. Use for code walkthroughs, onboarding explanations, placement or layering questions, and explicitly requested architecture critique.
qstack-loop-no-nonsense
Execute an approved implementation plan exactly, maintaining QStack execution evidence and requiring independent adversarial review.
qstack-loop-trequartista
Execute an approved implementation plan with documented adaptations, QStack execution evidence, and independent adversarial review.
qstack-make-operations-idempotent
Design or review commands, lifecycle steps, and processing loops so retries, partial failure, restart, and stale state converge to the same correct result. Use when an operation may run twice or resume after a crash.
qstack-next
Recommend the one installed skill to run next, from what the conversation has done so far and the state of the plan folder on disk. Use when invoked as /qstack-next, when asked "what now?" or which skill to use next, or as the last step of /qstack.
qstack-plan-prior-art
Read the project's existing plan folder as content and brief the planner on what was already decided, deferred, and learned. Runs standalone before anything is written, or from /qstack-plan-to-html once a Markdown draft exists and before the HTML document is. Ranks earlier plans by overlap with the subject being planned, then reports decisions already settled, questions never answered, where plans diverged from reality, live board cards owning the same files, what this plan supersedes, and rules already binding in the instruction files. Read-only: it writes nothing into the plan folder. Use before drafting or converting a plan, when asked whether something was planned before, or when new work may overlap work already recorded.
qstack-unslop
Rewrite the previous answer to remove AI writing patterns and add a natural human voice without losing meaning or useful detail.
qstack-build-the-lever
Build the smallest rerunnable tool that makes non-trivial work repeatable, reviewable, and safe to verify.
qstack-encode-lessons-in-structure
Turn a recurring correction or repeated instruction into the strongest practical structural guardrail. Use when the same mistake returns, prose is being repeated, or a rule could become a type, schema, lint, check, or script.
qstack-fix-root-causes
Reproduce and diagnose a failure until its root cause is supported by direct evidence. Use for debugging, recurring symptoms, restart-only failures, or a proposed guard that may only hide the real defect.
qstack-foundational-thinking
Settle data shape, access, ownership, concurrency, and useful shared setup before writing feature logic.
qstack-model-the-domain
Replace scattered domain assumptions with the smallest structure that removes invalid states and branching. Use when booleans have to be kept in sync, the same rule is validated at several call sites, a branch grows with every new case, or an invalid state can be represented at all.
qstack-prove-it-works
Verify completed work against the real artifact and its full input-to-output path instead of relying on compilation, timestamps, cached output, or agent summaries. Use before claiming a task or feature works.
qstack-separate-before-serializing-shared-state
Redesign concurrent work that shares a mutable file, branch, key, or state object by separating ownership before adding serialization. Use when actors may race, a lock is proposed, or coordination relies on taking turns.
qstack-serve-plans
Serve the current repository's QStack HTML plan collection on a chosen local address and port.
qstack-ask-plan-open-questions
Resolve material open questions in a QStack plan through one-at-a-time, plain-language decision dialogs, then write each answer and its consequences back into the plan immediately. Accepts a bootstrap Markdown plan or an authoritative QStack plan.html; once HTML exists, edits only HTML and never maintains a Markdown mirror. Use when invoked as /qstack-ask-plan-open-questions, when asked to resolve a plan's open questions, or automatically after /qstack-plan-to-html creates plan.html.
qstack-plan-adherence-review
Review whether an approved QStack HTML plan was faithfully executed by comparing plan.html with execution.md, executor.md, or legacy implementation notes and the actual committed and uncommitted code changes. Build a requirement-to-evidence matrix, identify missing or unapproved deviations, check whether the execution record matches reality, and assign a guarded 0-5 adherence score. Use when invoked as /qstack-plan-adherence-review, when asked whether a plan was followed, or before closing or landing planned work.
qstack-reflect
Produce an evidence-only report on how a project is actually being worked: checkout and branch topology, momentum over time, rework, instruction-file churn, and plan-record completeness. Every finding cites a count the reader can reproduce, and any category without enough evidence is refused rather than padded. Reads across every worktree Git tracks for the repository, not just the current checkout. Use when invoked as /qstack-reflect, optionally with one or more plan directories such as /qstack-reflect docs/rfcs, or when asked how the work is going, what patterns show up across checkouts, or where effort is being lost.
qstack-be-concise
Rewrite the immediately previous assistant answer in plain, non-technical language using far fewer lines. Use when the user invokes `/qstack-be-concise`, optionally with a target such as `/qstack-be-concise 4`, or asks to make the last answer shorter and simpler.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.