braingrid-cli

Plan software requirements and tasks using BrainGrid CLI commands.

20|Updated Oct 2, 2025
One-click install
npx skills add https://github.com/BrainGridAI/braingrid --skill braingrid-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: braingrid-cli
Source: https://github.com/BrainGridAI/braingrid/tree/main/claude-code/skills/braingrid-cli
Command: npx skills add https://github.com/BrainGridAI/braingrid --skill braingrid-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

BrainGrid CLI turns vague project ideas into structured requirements and actionable tasks, reducing ambiguity and rework.

Core Features & Use Cases

  • Guides users through initializing a BrainGrid project, refining ideas into requirements, breaking them into tasks, and tracking progress.
  • Enables consistent, AI-ready prompts and exportable build plans for teams.
  • Supports cross-project usage with auto-detection and flexible formatting for outputs.

Quick Start

Initialize your BrainGrid project with braingrid init, refine a prompt with braingrid specify --prompt "Add user authentication", break down with braingrid requirement breakdown REQ-1, and export the full plan with braingrid requirement build REQ-1.

Frequently Asked Questions about braingrid-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down software requirements into actionable tasks from a vague prompt?

Task breakdown converts high-level software requirements into granular, actionable development items. It reduces ambiguity by mapping structured prompts into sequential build plans and trackable task lists.

What's the best way to structure project specs for AI-ready development?

Structuring project specs for AI-ready development involves using spec-driven workflows to refine ideas into requirements and break them into tasks. This ensures consistent prompts and exportable build plans for teams.

How do I initialize a spec-driven project workflow for task breakdown?

Initialize a spec-driven project by running an init command to set up the environment, then refine prompts into formal requirements and break them into trackable tasks through the development lifecycle.

Does spec-driven task breakdown work for individual developers as well as teams?

Spec-driven task breakdown works for both individuals and teams needing structured specs and progress tracking. It supports cross-project usage with auto-detection and flexible output formatting.

Can I export a full build plan after breaking down a project requirement?

Yes, you can export a full build plan after breaking down a project requirement. The workflow converts specified requirements into a comprehensive build plan for development tracking.