Specsfy CLI
A methodology and CLI for single-spec development: skills install into a project and lead an agent from idea to verified code
- 88 ★ on the repository
- Last commit
Broad access
Why this level
- The deploy specialist manages servers through Ansible and Docker Swarm, and `./deploy run --non-interactive` rolls out without prompts using an external Vault password.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/specsfyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The deploy specialist manages servers through Ansible and Docker Swarm, and `./deploy run --non-interactive` rolls out without prompts using an external Vault password.
This is third-party code. Review the repository files before installing.
What it does
Specsfy builds development around a single executable specification and keeping requirements, tests and code in one verifiable loop. The project motto, "Especifique. Prove. Entregue.", means specify, prove, deliver. The `specsfy` CLI installs the methodology skills into a project and optional technical specialists on request. The agent goes step by step: `$specsfy-01-inbox` saves the original wording in `specs/inbox/`, `$specsfy-02-backlog` turns it into a numbered item, and further skills lead to specification, tests and code. CLI commands: `specsfy doctor --project .` checks the environment, `specsfy install --project .` installs skills, `specsfy update` updates project skills and `specsfy upgrade` updates the CLI itself. In a GitHub Spec Kit project the `$specsfy-setup` skill reads `.specify/memory/constitution.md` and the `specs/` folder and writes a `.specsfy/SPECKIT.md` bridge, leaving the original files alone. A `specsfy-specialist-deploy` specialist covers release and production on Docker Swarm.
Who it is for. Teams that build a product with an agent and want the specification, tests and code to stay consistent and verifiable.
Good fit when
- An idea is first captured in the inbox and then taken to backlog and specification without spreading across plan.md and tasks.md
- A project already runs on GitHub Spec Kit and needs a bridge to the methodology with no file moves
- Methodology skills have to be installed and updated in a project with `specsfy install` and `specsfy update`
- Release and Docker Swarm servers are handled through the deploy specialist with an Ansible inventory
Not a fit when
- A small fix or prototype, where the full cycle from inbox to specification takes longer than the work
- You want only a general skill set with no methodology and no backlog
- Node.js 22.20 or newer is missing, and the CLI requires it
Example request
Use $specsfy-01-inbox and save the idea: a /boas-vindas page that greets the visitor by nameLimitations
Node.js 22.20 or newer, npm and the `skills` command or `npx` are required. Documentation and skills are written in Portuguese, and the tutorial example uses Laravel and Pest. If the repository is private, a case the README covers, a one-time `gh auth login` is needed, and automation sets `GH_TOKEN` or `GITHUB_TOKEN` with read access. For agent-run deploys, `./deploy configure-vault` prepares an external Vault password and `./deploy run --non-interactive` uses it without prompts, so grant such access deliberately. The framework, CLI and skills share a single version.
How to disable. Remove the package with `npm uninstall --global @promovaweb/specsfy` and the skills installed in the project, and keep or delete the `specs/` and `.specsfy/` files as needed.
FAQ
How do I install Specsfy?
Run `npm install --global @promovaweb/specsfy`, then in the project folder `specsfy doctor --project .` and `specsfy install --project .`. Check the version with `specsfy --version`.
How do I update skills and the CLI itself?
`specsfy update --project .` updates the project skills and `specsfy upgrade` updates the CLI.
What does the $specsfy-01-inbox skill do?
It saves the original wording in `specs/inbox/` as a file with a date, time and slug. It asks no questions, creates no backlog and changes no code.
Does Specsfy work with Spec Kit?
Yes. The `$specsfy-setup` skill reads `.specify/memory/constitution.md` and the `specs/` folder and publishes a `.specsfy/SPECKIT.md` bridge, with the original artifacts staying in place.
Can the agent roll out releases by itself?
Only if you set up `./deploy configure-vault`, after which `./deploy run --non-interactive` uses the external Vault password without prompts. A manual deploy still asks for the password.
Discussion
No questions or reviews yet.
Related
CLI toolsGitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
A CLI, MCP server and skill for spec-driven development: short markdown specs, a task board and search that an agent can read.
Two skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
A terminal environment and CLI for spec-driven development: Gherkin, a task board and several agents, written in Rust.
A CLI that keeps the spec, tasks and proof of done in git so Claude, Codex, Grok and Cursor can hand work to each other
The spxa CLI and a skill set for spec-driven development in Claude Code, Codex and Cursor, from a change proposal to the archive
README in short
The README presents a monorepo with the methodology, specialists, CLI, docs and an example, gives npm and `specsfy install` setup, and describes the Spec Kit bridge, Ansible and Vault deploys and brand material builds.