Zero configuration. No GitHub Actions to configure. No CI YAML to write. Just specs in, PRs out.
UseZombie milestone specs
The native spec format organizes work into a hierarchy: Milestones, Workstreams, Sections, and Dimensions.
# M4_002: Publish npm package
**Prototype:** v1.0.0
**Milestone:** M4
**Workstream:** 002
**Date:** Mar 29, 2026
**Status:** PENDING
**Priority:** P0 — Critical path for CLI distribution
**Batch:** B1 — parallel execution group
**Depends on:** M4_001
---
## 1.0 Package configuration
**Status:** PENDING
Configure package.json, entry points, and build output for npm publish.
**Dimensions:**
- 1.1 PENDING package.json has correct name, version, and bin field
- 1.2 PENDING Build output matches declared entry points
- 1.3 PENDING README included in published package
---
## 2.0 Acceptance criteria
**Status:** PENDING
- [ ] 2.1 npm pack produces a valid tarball
- [ ] 2.2 npx zombiectl --version prints the correct version
- [ ] 2.3 Global install resolves the binary to PATH
OpenSpec by Fission AI
OpenSpec is an open-source spec framework that stores structured artifacts in git. Specs are organized as proposal, design, and task documents in markdown.
UseZombie reads OpenSpec artifacts and uses them as agent context. No conversion step needed — submit the spec file directly.
gstack /autoplan
gstack’s /autoplan command produces structured plans through a CEO, engineering, and design review pipeline. The output is a markdown plan with sections, tasks, and acceptance criteria.
Submit the generated plan markdown as a spec. UseZombie treats it like any other spec file.
Plain markdown
No framework required. A plain markdown file describing what you want is a valid spec.
# Add dark mode toggle to the settings page
Users should be able to switch between light and dark themes
from the settings page. The preference should persist in
localStorage and apply immediately without a page reload.
The toggle should be a switch component matching the existing
design system in src/components/ui/Switch.tsx.
