Get Buildforce running in your project and complete your first spec-driven workflow in minutes.
Install the @buildforce/cli package globally:
npm install -g @buildforce/cli
Or use npx without installing:
npx @buildforce/cli init .
Initialize Buildforce in an existing project:
buildforce init .
Or create a new project:
buildforce init my-project

During initialization, select your AI assistant:
Buildforce will install slash command files into your assistant's configuration folder (e.g., .cursor/commands/).
Open your AI assistant in any existing project and run this workflow:
/research the architecture and structure of this codebase
/spec Update README.md to fix any inconsistencies with actual project structure and features
/build
/complete
This workflow works on any codebase! Here's what happens:
/research - Gather ContextBuildforce searches your context repository, explores your codebase, and produces a structured report with:
Research findings stay in context to inform your spec.
/spec - Define RequirementsConverts your description into structured requirements:
spec.yaml (WHAT to build) with functional requirements, acceptance criteria, and scopeplan.yaml (HOW to build) with architecture decisions, phases, and tasks/build - Execute ImplementationFollows the plan systematically:
/complete - Finalize and Save KnowledgeValidates everything is done:
.buildforce/context/ that will inform future work. Each completed feature makes your context repository smarter./research gathered existing context before requirements/spec converted your request into structured requirementsThis is context-first spec-driven development in action.
Now that you've seen the workflow, dive deeper:
/researchBefore building any feature, run /research [your-topic] to load relevant context. This ensures your specs are informed by existing patterns and past decisions.