Zhi Zheng
Community@elebirds · Shanghai, China
Zhi Zheng (elebirds) maintains Trellis, a spec-driven development framework that injects project conventions, requirements discovery, and quality gates into coding sessions.
Agent Skills by Zhi Zheng
Showing 8 vetted skills indexed across 1 GitHub repositories.
elebirdstrellis-before-dev
Loads project-specific coding guidelines from .trellis/spec before writing code.
elebirdstrellis-brainstorm
Guides collaborative requirements discovery and converges on an MVP scope before implementation.
elebirdstrellis-break-loop
Analyzes fixed bugs across five dimensions to produce prevention mechanisms and spec updates.
elebirdstrellis-check
Verifies code changes against specs, lint, tests, and cross-layer consistency checklists.
elebirdstrellis-meta
Guides customization of local Trellis workflow, hooks, agents, and platform files.
elebirdstrellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documentation files.
elebirdstrellis-finish-work
Archives completed tasks and records session journals after verifying a clean git working tree.
elebirdstrellis-continue
Resumes in-progress tasks by loading the Trellis workflow phase index and step context.
Frequently Asked Questions About Zhi Zheng
FAQPage SchemaWhat tasks can I accomplish with elebirds' Trellis skills?▼
The eight Trellis skills cover the full coding lifecycle: discovering project specs before coding, brainstorming requirements into a PRD, verifying quality via lint/type-check/tests, capturing conventions into .trellis/spec/, analyzing bug root causes, resuming in-progress tasks, and archiving completed sessions.
Who should use the Trellis skill set?▼
Software engineers and developers working on multi-package projects who want persistent, spec-driven conventions across sessions. It suits teams that need requirements discovery, quality gates before commits, and knowledge capture to prevent recurring bug classes.
How does a typical Trellis session run from start to finish?▼
Start with trellis-before-dev to load specs, use trellis-brainstorm for unclear requirements, verify with trellis-check before committing, then close with trellis-finish-work to archive tasks and log the developer journal. Resume later via trellis-continue.
What prerequisites does Trellis require?▼
A project initialized with trellis init, which generates the .trellis directory containing spec/, platform hooks, settings, agents, skills, commands, and prompts. Resuming tasks also relies on the get_context.py script with --mode phase for step-level detail.
How does Trellis prevent repeated bugs?▼
The trellis-break-loop skill performs deep root-cause analysis after a fix, examining why prior fixes failed and which prevention mechanisms apply. Findings are captured into specs via trellis-update-spec so future sessions inherit the knowledge.