spec-consistency
Checklist that keeps every artifact of the Harnessfile spec in sync — spec prose, JSON Schemas, CLI validator, UI validation, examples, README. Run before closing any spec-facing change and during review of one.
- License 许可
- Apache-2.0
- 最近更新
- 2026-09-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- spec-consistency
- description
- Checklist that keeps every artifact of the Harnessfile spec in sync — spec prose, JSON Schemas, CLI validator, UI validation, examples, README. Run before closing any spec-facing change and during review of one.
03 SKILL.md 正文
Spec consistency
The spec is one artifact expressed in six places. A spec-facing change is done only when all of them agree. Walk the checklist; every "no" is a finding.
The sync surface
| Artifact | Path | What must agree |
|---|---|---|
| Spec prose | spec/v0.2-draft.md |
fields, defaults, semantics (normative) |
| JSON Schemas | schema/*.json |
every field in prose exists here with the same default/enum |
| CLI validator | packages/cli/src/validator/validate.ts (+ ir/normalize.ts defaults) |
same checks, same defaults |
| UI validation | ui/src/lib/validate.ts (+ ui/src/types.ts) |
mirrors the CLI checks it can run client-side |
| Examples | examples/minimal, examples/altavox |
still valid; new fields demonstrated when user-facing |
| README | README.md |
core-ideas and examples sections not contradicted |
Checklist
- Grep the changed field/concept across all six paths — every occurrence updated or consciously exempted.
cd packages/cli && npm test— green.npx tsx bin/harnessfile.ts validate ../../examples/minimaland../../examples/altavox— both valid.cd ui && npm run build— clean (when UI surface changed).- Defaults stated in prose match
normalize.tsand the schemas (default:keys). - Decision recorded (decision-record skill) when the change alters what the standard says.
Smell tests
- A field only in the schema, or only in prose → inconsistency.
- The CLI accepts what the schema rejects (or vice versa) → inconsistency.
- An example that no longer round-trips through the UI byte-identical → regression.
04 同仓库更多 Skills
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.
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`).
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.
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.
ponytail
Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.
ponytail-review
Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.