multi-agent-collaboration-system: Skill for Claude Code

Update Code-Spec - Capture Executable Contracts

When you learn something valuable (from debugging, implementing, or discussion), use this skill to update the relevant code-spec documents.

Timing: After completing a task, fixing a bug, or discovering a new pattern

---

Code-Spec First Rule (CRITICAL)

In this project, "spec" for implementation work means code-spec:

• Executable contracts (not principle-only text)
• Concrete signatures, payload fields, env keys, and boundary behavior
• Testable validation/error behavior

If the change touches infra or cross-layer contracts, code-spec depth is mandatory.

Required sections for infra/cross-layer specs:

1. Scope / Trigger
2. Signatures (command/API/DB)
3. Contracts (request/response/env)
4. Validation & Error Matrix
5. Good/Base/Bad Cases
6. Tests Required (with assertion points)
7. Wrong vs Correct (at least one pair)

---

When to Update Code-Specs

Trigger	Example	Target Spec
Implemented a feature	Added template download with giget	Relevant backend/ or frontend/ file
Made a design decision	Used type field + mapping table for extensibility	Relevant code-spec + "Design Decisions" section
Fixed a bug	Found a subtle issue with error handling	backend/error-handling.md
Discovered a pattern	Found a better way to structure code	Relevant backend/ or frontend/ file
Hit a gotcha	Learned that X must be done before Y	Relevant code-spec + "Common Mistakes" section
Established a convention	Team agreed on naming pattern	quality-guidelines.md
New thinking trigger	"Don't forget to check X before doing Y"	guides/*.md (as a checklist item, not detailed rules)

Key Insight: Code-spec updates are NOT just for problems. Every feature implementation contains design decisions and contracts that future AI/developers need to execute safely.

---

Spec Structure Overview

.trellis/spec/
├── backend/           # Backend coding standards
│   ├── index.md       # Overview and links
│   └── *.md           # Topic-specific guidelines
├── frontend/          # Frontend coding standards
│   ├── index.md       # Overview and links
│   └── *.md           # Topic-specific guidelines
└── guides/            # Thinking checklists (NOT coding specs!)
    ├── index.md       # Guide index
    └── *.md           # Topic-specific guides