Use to check manifest, ledger, document or surface validity against schema rules.
中文简介正在准备中。当前显示原文说明。
74 个(tvproductions 的仓库) · 按人气排序
Use to check manifest, ledger, document or surface validity against schema rules.
中文简介正在准备中。当前显示原文说明。
Use for repository hygiene; reports governance maintenance findings and regenerates surfaces with --fix.
中文简介正在准备中。当前显示原文说明。
Use when gates are green but code still looks Java-flavored, to surface Pythonic refactor candidates.
中文简介正在准备中。当前显示原文说明。
Use for a tech-debt review of files, paths, ADRs, OBPIs or the repo; produces a prioritized report.
中文简介正在准备中。当前显示原文说明。
Use when exiting plan mode or before implementing to verify ADR intent, OBPI scope and plan agree.
中文简介正在准备中。当前显示原文说明。
Use after gz-pythonic-pattern-detect marks a candidate applied, to capture the rewrite's before/after proof.
中文简介正在准备中。当前显示原文说明。
Use to reconcile OBPI briefs and the ADR table against the ledger and report what only the operator can resolve.
中文简介正在准备中。当前显示原文说明。
Use to define or revise project-level intent as a PRD before ADR planning.
中文简介正在准备中。当前显示原文说明。
Run a governed R&D session — diamond 1 of the double diamond, which defines the problem and names which fan-out artifacts are warranted. Use when the operator pastes external material and says "consider this for gzkit", asks "is there something here gzkit is missing or could improve on", opens an exploratory design discussion whose outcome is not yet known, or asks why a class of defects keeps recurring and how the issues carrying it should be restructured. Ends at a six-row disposition map and operator sign-off; produces no fan-out artifact itself. Operator-invoked only.
中文简介正在准备中。当前显示原文说明。
Use for status inquiries, blockers and next actions; reports workflow fronts with ADR lifecycle and gates.
中文简介正在准备中。当前显示原文说明。
Namespace router → end-to-end workflow skills (design through release). Use to pick the next workflow stage before invoking the matched concrete skill directly.
中文简介正在准备中。当前显示原文说明。
Namespace router → project lifecycle skills (init, requirements, constitution, status). Use to pick the project-level intent before invoking the matched concrete skill directly.
中文简介正在准备中。当前显示原文说明。
Use after a plan is approved, or when the operator says "execute OBPI-X.Y.Z-NN", to implement, verify and sync an OBPI.
中文简介正在准备中。当前显示原文说明。
Use to create an ADR, a pool ADR included, recording architecture intent and lane scope.
中文简介正在准备中。当前显示原文说明。
Use after an OBPI's implementation, before reconcile, to review its code for reuse, quality and efficiency.
中文简介正在准备中。当前显示原文说明。
Use to decompose an ADR item into an authored OBPI brief.
中文简介正在准备中。当前显示原文说明。
Run the guarded repository sync ritual; the hooks your pre-commit config declares enforce the quality gates.
中文简介正在准备中。当前显示原文说明。
Use to sweep the governance shape, trace a node's lineage, diff against the last sweep, or read its blast radius.
中文简介正在准备中。当前显示原文说明。
Use to run a GHI-driven patch release, or to publish a minor release handed over by gz closeout.
中文简介正在准备中。当前显示原文说明。
Namespace router → quality and complexity skills. Use to pick the quality-check intent before invoking the matched concrete skill directly.
中文简介正在准备中。当前显示原文说明。
Use to review a skill by re-verifying its claims against the code it wields, then correct it and move last_reviewed.
中文简介正在准备中。当前显示原文说明。
Use to report artifact lineage, relationships or readiness.
中文简介正在准备中。当前显示原文说明。
Use to claim, release or list OBPI work locks.
中文简介正在准备中。当前显示原文说明。
Use to create or resume a session handoff document.
中文简介正在准备中。当前显示原文说明。