Skip to main content

kevglynn/house-rules

SkillsMP は kevglynn/house-rules から 16 件の skill を収集しています。skill を開くとソースと詳細を確認できます。

記録された最新のソース活動
SkillsMP カタログ更新
収集済み skills
16
GitHub スター
0
GitHub フォーク
0

収集済み skill 16 件中 16 件を表示しています。

職業分類
ソフトウェア品質保証アナリスト・テスター
説明

Run a Tier 2 cross-model review handoff on a Tier-1-reviewed chunk of work: gather the bead context, changed files, Tier 1 outcomes, and trusted boundary; draft the review-focus paragraph; call the deterministic assembler to emit a ready-to-paste prompt…

原文の言語: 英語

更新
職業分類
テクニカルライター
説明

Voice discipline for human-facing prose — pattern catalog, self-correction protocol, and worked examples for killing AI-sounding rhetorical tics. Load when writing positioning docs, pre-whitepapers, packets, deck copy, primers, emails, briefs, or any prose a…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Whole-repo audit for over-engineering. Like graybeard-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Quick-reference index for the graybeard family: which skill or rule to use for over-engineering review, repo-wide audit, defer-ledger harvesting, or minimal-implementation mode. One-shot display, not a persistent mode. Trigger: "graybeard help", "use…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says…

原文の言語: 英語

更新
職業分類
プロジェクト管理専門家
説明

Author a gate/sprint review packet from a committed blueprint: gather the gate's bead evidence and receipts, populate the reader's-own-checklist status grid with a divergence strip, a capped FAQ, and exactly three linked receipts, carry the decision…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Harvest every `defer:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals get tracked instead of rotting into "later means never". Use when the user says "graybeard debt", "/graybeard-debt", "what did we defer", "list the…

原文の言語: 英語

更新
職業分類
その他コンピュータ職
説明

Single-bead lifecycle playbook — authoring worked examples (bd create with description/ACs/non-goals), dedupe search, validation mechanics (bd lint / --dry-run), wisps, JIT verification on pickup, progress notes, self-review before close, close-reason format…

原文の言語: 英語

更新
職業分類
その他コンピュータ職
説明

Planner playbook for multi-bead breakdowns — decomposition heuristics, atomic dependency-graph creation with bd create --graph, graph verification, and mid-flight epic management (stuck children, scope expansion, honest epic close). Trigger phrases: "plan…

原文の言語: 英語

更新
職業分類
ソフトウェア品質保証アナリスト・テスター
説明

Run a Tier 1 same-model multi-lens review of a completed chunk of work: dispatch independent review subagents (code-reviewer, architect-reviewer, simplify, and — when the change involves tests or a no-test claim — test-signal) in parallel with a complete…

原文の言語: 英語

更新
職業分類
ソフトウェア品質保証アナリスト・テスター
説明

Per-bead-type TDD playbooks — the operational procedure behind the pragmatic-tdd rule. Use when starting a bug/feature/refactor bead, when you need to write the failing test, or when proving red-then-green after the fact. Triggers on "pragmatic tdd",…

原文の言語: 英語

更新
職業分類
その他コンピュータ職
説明

Convene a council of diverse AI voices to analyze a task from multiple perspectives using different models. Each voice operates as a full-capability generalPurpose subagent (reads, shell, MCPs) with its own analytical lens. Synthesizes perspectives rather…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Structured approach to diagnosing and fixing bugs. Use when a bug is reported, a test fails unexpectedly, behavior doesn't match expectations, or when "something is wrong" but the cause isn't clear. Triggers on "debug this", "why is this broken", "this…

原文の言語: 英語

更新
職業分類
プロジェクト管理専門家
説明

Run a deliberate, evidence-grounded audit of a project's intent, plan, execution, and operating mechanisms, producing a classified refinement proposal — a structured recommendation for change, or an explicit confirmation that no change is needed. Covers…

原文の言語: 英語

更新
職業分類
ソフトウェア開発者
説明

Validate a drafted gate/sprint packet with a four-lane deep-dive: accuracy-vs-repo, cold-read (the overlay's reader persona and access boundary), receipts verification (re-run every count/string/exit-code live), and navigability/structure — with a phase-2…

原文の言語: 英語

更新
職業分類
プロジェクト管理専門家
説明

Orients an agent in a new or resumed workspace by reading the canonical orientation files (CLAUDE.md, AGENTS.md, .cursor/scratchpad.md, and PLAN.md if present), summarizing what the workspace is for, current status, and the top blockers and next actions —…

原文の言語: 英語

更新
収集済み skill 16 件中 16 件を表示しています。