
ecodan/cicadas
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Spec informed, code authoritative SDD built for teams
개요
Cicadas reverses the traditional relationship between code and documentation. Instead of fighting to keep specifications in sync with code, that drive implementation and then expire. Authoritative system documentation is then into canonical snapshots. 1. : PRDs, designs, and task lists drive implementation but expire when the initiative completes. 2. : The codebase is the only source of truth. 3. : Parallel initiatives and features are registered in a registry, allowing parallel work efforts to minimize overlap and clashes. 4. : Authoritative documentation (canon/) is generated from the code + the intent of expired specs. It is never manually maintained, and larger repos use a more selective canon structure than smaller ones. 5. : During development, we keep specs honest via (updating active specs to match code reality) and coordinate via (broadcasting breaking changes to peer branches). This downloads Cicadas into .cicadas-skill/cicadas/, initializes the .
README
원문 README의 일부입니다. 원문 보기.
Cicadas
Version 1.0.0
Sustainable, Spec-Driven Development (SDD) for human-AI teams.
Cicadas reverses the traditional relationship between code and documentation. Instead of fighting to keep specifications in sync with code, Cicadas treats forward-looking docs (PRDs, plans) as disposable inputs that drive implementation and then expire. Authoritative system documentation is then reverse-engineered from the code itself into canonical snapshots.
The Core Concept
- Active Specs are Disposable: PRDs, designs, and task lists drive implementation but expire when the initiative completes.
- Code is Truth: The codebase is the only source of truth.
- Work is Coordinated: Parallel initiatives and features are registered in a registry, allowing parallel work efforts to minimize overlap and clashes.
- Canon is Synthesized: Authoritative documentation (
canon/) is generated from the code + the intent of expired specs. It is never manually maintained, and larger repos use a more selective canon structure than smaller ones. - Reflect & Signal: During development, we keep specs honest via Reflect (updating active specs to match code reality) and coordinate via Signal (broadcasting breaking changes to peer branches).
Getting Started
Installation
One-liner (requires Python 3.11+ and git):
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash
This downloads Cicadas into .cicadas-skill/cicadas/, initializes the .cicadas/ workspace, and optionally sets up agent integrations. Re-running initialization is idempotent: existing registry, index, config, and active state are preserved.
With agent integration:
# Claude Code
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --agent claude-code
# Codex
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --agent codex
# Cursor
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --agent cursor
# Rovodev
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --agent rovodev
# Multiple agents
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --agent claude-code,codex
Custom install directory:
bash install.sh --dir tools/cicadas --agent claude-code
Update Cicadas files (preserves your .cicadas/ workspace):
bash install.sh --update
- or -
curl -fsSL https://raw.githubusercontent.com/ecodan/cicadas/master/install.sh | bash -s -- --update
Supported agents:
| Agent | Integration |
|---|---|
claude-code |
.claude/skills/cicadas symlink (uses project CLAUDE.md if present) |
antigravity |
.agents/skills/cicadas symlink |
추천 도구
다른 키워드를 입력하거나 필터를 제거해 보세요.
설치
npx skillfish add ecodan/cicadas