zjx avatar

zjx

Community

@zhangliuliuzhang · 中国

1Followers
|
9Public Repos
|
11Published Skills

zjx publishes GitHub Spec Kit command skills enabling spec-driven development: feature specification, planning, task generation, analysis, and implementation within .specify/ project structures.

Skills Distribution
DomainDeveloper To...Spec-Driven Develo.. (40%)Task & Issue Manag.. (25%)Requirements Clari.. (20%)Project Governance.. (15%)

Agent Skills by zjx

Showing 11 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About zjx

FAQPage Schema
What tasks can I perform using zjx's Spec Kit skills?

You can create feature specifications from natural language, clarify underspecified requirements, generate implementation plans and dependency-ordered tasks, analyze cross-artifact consistency, execute tasks.md implementation, convert tasks to GitHub issues, and maintain project constitutions and checklists.

Who should use these Spec Kit command skills?

Software engineers, technical leads, and product-minded developers practicing spec-driven development benefit most. They suit teams who want structured spec.md, plan.md, and tasks.md artifacts governing feature work rather than ad-hoc prompting, plus maintainers syncing coding agent context files.

What are the prerequisites for running these skills?

Every skill requires an existing spec-kit project structure containing a .specify/ directory. You must initialize the Spec Kit templates in your repository first; the skills then operate on the spec.md, plan.md, and tasks.md artifacts within that structure.

How do the skills fit together in a typical feature lifecycle?

Start with speckit-specify to draft the spec, use speckit-clarify to resolve ambiguities, run speckit-plan and speckit-tasks for design artifacts, validate with speckit-analyze, then execute via speckit-implement. speckit-converge appends remaining work, and speckit-taskstoissues publishes GitHub issues.

Are these Spec Kit skills free to use?

The skills originate from github-spec-kit templates (templates/commands/ sources), which are openly distributed. No licensing fees or paid tiers are indicated in the manifest; they are user-invocable commands requiring only a spec-kit project structure to operate.