Tag: cursor

Categoria: Workflows/SDD

- Project Overview - Agent Manual

Categoria: Workflows/SDD

Implement the three core SDD commands (/specify, /plan, /tasks) as Cursor IDE commands to enable structured software development workflow.

Categoria: Workflows/SDD

A Spec-Driven Development toolkit for Cursor IDE (v2.5+) that provides structured commands, subagents, and skills for feature specification, planning, and parallel execution.

Categoria: Workflows/SDD

Tasks break a Plan into ordered, independently completable units. Only generate a tasks.md for Project scope (multi-day work). For Quick or Feature scope, the agent's todo list is enough.

Categoria: Workflows/SDD

The spec answers what and why — never how. No frameworks, libraries, file paths, function names, or implementation details. If a non-technical PM could write it, you're at the right level.

Categoria: Workflows/SDD

The boring-but-critical pass. Run before declaring a feature done. The difference between "compiles and runs" and "delightful in production" is in this list.

Categoria: Workflows/SDD

The plan answers how. Built only after the spec is signed off. Under 2 minutes to read — if longer, the feature is too big; split it.

Categoria: Workflows/SDD

How to ask the right questions, organized by request type. Pick 2–5 questions total — never run the full list. Questions are ordered most-to-least important; start at the top.

Categoria: Workflows/SDD

A worked example of how the Quick path looks in practice. Total interaction: one round of questions, an inline mini-spec, a thumbs-up, then build.

Categoria: Workflows/SDD

A worked example of Project scope: spec + plan + tasks as files in specs//. For multi-day work where the artifacts pay for themselves.

Categoria: Workflows/SDD

A worked example of a Feature-scope flow: full spec + plan, but no separate tasks file. Typical for 1–4 hours of work.

Categoria: Workflows/SDD

User requests for features are incomplete by design — the user gives you the top-of-mind 30%, not the full spec. Coding from that ships things that compile but miss the actual intent, skip the boring-but-critical states (loading, empty, error, edge), and feel unpolished.

Categoria: Workflows/SDD

A VS Code sidebar extension view with three tabs (Bolts, Specs, Overview) that displays project state derived from parsed markdown frontmatter. The UI is a pure representation of a centralized metadata state object - it does not perform parsing or state management.

Categoria: Workflows/SDD

See what AI is building. Track every run, intent, and change.

Categoria: Workflows/SDD

Purpose: This document captures the complete architecture plan for adding FIRE flow support to the VS Code extension with multi-flow switching capability.

Categoria: Workflows/SDD

This guide covers architecture, development setup, and publishing for maintainers.

Categoria: Workflows/SDD

Create a research agent or explore flow that generates exploration outputs consumable by all three AI-DLC phases (Inception, Construction, Operations).

Categoria: Workflows/SDD

Use this template when generating tasks.md for a feature spec.

Categoria: Workflows/SDD

Use this template when generating requirements.md for a feature spec.

Categoria: Workflows/SDD

Use this template when generating design.md for a feature spec.

Categoria: Workflows/SDD

Generate an implementation plan with coding tasks based on the approved design. This is Phase 3 of the spec-driven development workflow.

Categoria: Workflows/SDD

Generate a requirements document for a feature using EARS (Easy Approach to Requirements Syntax) format. This is Phase 1 of the spec-driven development workflow.

Categoria: Workflows/SDD

Execute implementation tasks from an approved tasks.md file. This is the post-spec execution phase.

Categoria: Workflows/SDD

Generate a technical design document based on approved requirements. This is Phase 2 of the spec-driven development workflow.