design
Draft design.md for an OpenSpec change on the design track: file:line context, options with trade-offs, the adopter seam, and owner questions. Read-only on code; drafts and never rules or implements.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- design
- description
- Draft design.md for an OpenSpec change on the design track: file:line context, options with trade-offs, the adopter seam, and owner questions. Read-only on code; drafts and never rules or implements.
03 SKILL.md 正文
Draft a Design
Read the architect contract first; it names the protocol sections a design needs. Use this skill only on the design track (protocol § 2 step 1, Clarify); a quick change has no design.md. You draft text; the owner rules and a developer implements.
1. Inventory What Exists
Open every file the change touches and record each claim as file:line, opened in this session, never remembered. Run git log -S '<symbol>' before calling anything dead.
2. Write design.md in OpenSpec's Sections
Write openspec/changes/<id>/design.md with the spec-driven sections (Context, Goals / Non-Goals, Decisions, Risks / Trade-offs, Migration Plan, Open Questions) and follow the design rules in openspec/config.yaml when present:
- Context: the
file:lineinventory from step 1. - Decisions: each names at least two options with cost, blast radius, and what each forecloses, plus the adopter seam: what a developer who never opened this file must know, and what happens if they do nothing.
- Open Questions: mark each one that needs an owner ruling. A question that would change specs, approach, or tasks is resolved before tasks.
Stay under 120 lines; task spec:check warns past the limit.
3. Tie Tasks to Premises
Give each task in tasks.md its file:line premise and its acceptance check. Leave the first task's Hold: OPEN-Q proposal awaits owner approval in place: one owner edit approves proposal.md and design.md together. Stop there and hand off.
04 同仓库更多 Skills
semengine-status
Report SemEngine Slice 04A package port progress, active PR claims, known flakes, and GitHub milestone/issue queue hygiene, and sync the GitHub Project v2 tracker. Use when asked for port status, auditing the issue queue, or updating the project board.
review-pr
Adapter for review-pr.
query-pattern
Choose how code reads the graph: graph-ingest's declared request verbs, the typed exact-entity reader, or an owner's bucket access. Use when a component or a consumer needs to read entities.
preflight
Select and run the existing SemEngine verification gates for a concrete diff before an implementation push or local-readiness assessment.
ponytail
Adapter for ponytail.
pickup
Adapter for pickup.