AGENT SKILL

decision-record

Record a design decision in decisions.md following the project's D-number process — numbering, redaction of superseded decisions, contradiction check, and spec update. Use whenever a design decision is made, changed, or found to conflict with existing ones.

License 许可
Apache-2.0
最近更新
2026-09-28
Stars
★ 0
Forks
0

01 前言 Front Matter

name
decision-record
description
Record a design decision in decisions.md following the project's D-number process — numbering, redaction of superseded decisions, contradiction check, and spec update. Use whenever a design decision is made, changed, or found to conflict with existing ones.

03 SKILL.md 正文

Decision record

All design decisions live in decisions.md as a chronological record. This skill is the process (from CLAUDE.md, D30):

Recording a new decision

  1. Find the highest existing D-number; the new decision is the next one.
  2. Add it under the current session heading (create one: ## Session N — <title> (YYYY-MM-DD) with a Source: line) as:
    ### D<n>: <short imperative title>
    **Decision:** <what was decided, in one or two sentences>
    **Rationale:** <why — optional but preferred>
    **Impact:** <what it changes — optional>
    
  3. Include the user's verbatim words as a User quote: when they capture the intent better than a paraphrase.

Superseding

If the new decision replaces an earlier one:

  • Mark the old title with [redacted by D<n>], strike through its original text (~~...~~), and add a **Superseded:** note pointing forward.
  • If only part of it is replaced, use [amended by D<n>] and add an **Amended:** note — no strikethrough.

Contradiction check

Before finishing, scan existing decisions for conflicts with the new one. A contradiction is never resolved silently: surface it to the human with both decisions quoted and ask which one stands.

Spec update

A decision is not done until spec/ (current draft) reflects it. Schemas in schema/ follow in the same change when the decision has a field-level surface.

04 同仓库更多 Skills

diegoquinteiro
diegoquinteiro/harnessfile

wireframe

Produce low-fidelity wireframes or storyboards to explore a flow, layout, or idea across multiple options before committing to hi-fi design. Use when the user wants to 'explore options', 'sketch something out', 'see a few directions', or when the problem is open enough that hi-fi work would be wasted.

★ 0
diegoquinteiro
diegoquinteiro/harnessfile

video-test

Record a video test of any feature or user flow via Playwright. Use when the user says "record video test", "video test", "record a test", "show me the feature", "record the UI", "capture video", or wants a visual demo of a feature. Accepts a description of what to test as an argument (e.g., `/video-test the brainstorm creation flow`).

测试与质量图像与多媒体
★ 0
diegoquinteiro
diegoquinteiro/harnessfile

risk-assessment

Assess the delivery risk and ambiguity of an issue. Scores three anchored 1-5 risk dimensions — Code Blast Radius, Complexity, Business Blast Radius — into an overall risk level (Low/Medium/High) with safeguards, plus a separate Ambiguity score (how many open questions remain) with the open questions listed. Use this BEFORE work starts, whenever someone wants to know how risky, how big, how complex, or how well-specified an issue is, or asks to "assess risk", "risk assessment", "score this issue", "how risky is this", "what's the blast radius", "how complex is this", "how ambiguous is this", or "how many open questions are there". Accepts a Multica issue ID, a GitHub issue/PR, or a free-text description as the argument.

★ 0
diegoquinteiro
diegoquinteiro/harnessfile

research

Deep parallel codebase research before planning or implementation. Spawns 4 specialized agents that explore behavior, architecture, coding standards, and test coverage simultaneously, then synthesizes findings into a structured RESEARCH.md document. Use this skill when the user says "research", "investigate", "explore the codebase", "understand the code", "deep dive", or wants thorough analysis of an area before making changes. Also use it as the first step of any complex feature — research first, then plan, then implement.

资料检索与研究
★ 0
diegoquinteiro
diegoquinteiro/harnessfile

ponytail

Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.

★ 0
diegoquinteiro
diegoquinteiro/harnessfile

ponytail-review

Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.

★ 0