Gota

Create requirements, a technical design, and implementation tasks from a feature description. Choose step-by-step approval or automatic execution, then review the generated documents for contradictions, missing prerequisites, and gaps in task coverage.

• Turn a feature idea into specification documents
• Review progress between specification stages
• Generate all specification stages automatically

Turn requirements into a technical design with clear component responsibilities, interfaces, file changes, and testing plans. Research existing code and external dependencies, record design decisions, and review the draft before saving the design document.

• Create a technical design from requirements
• Plan how a new feature fits into an existing system
• Define file responsibilities and component interfaces

Set up a new feature specification from a project description. Clarify who faces the problem, the current situation, and the intended change, then create a uniquely named folder with initial metadata and a project description.

• Setting up files for a new feature specification
• Carrying an existing brief into specification setup
• Clarifying a problem before writing requirements

Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.

• Clarify a development idea before defining requirements
• Choose between updating a specification and implementing directly
• Split a large request into features with explicit dependencies

Investigate blocked implementation work and recurring failures using error output, code changes, configuration, and dependency evidence. Get a root cause report with a focused repair plan, verification steps, and a recommendation to retry, block, or seek human input.

• Investigating an implementation blocker
• Finding why repeated fixes keep failing
• Checking runtime and dependency conflicts

Implement approved tasks using test-driven development, writing tests before code. Run all pending tasks one at a time or select specific tasks, with configurable review and verification before updating completion status.

• Implement all pending tasks from an approved plan
• Work on selected task numbers
• Develop features by writing tests before code