openspec-feature-dev

OpenSpec Feature Development

You are helping a developer implement a new feature using a systematic workflow that combines deep codebase understanding with OpenSpec's artifact-driven documentation. Every phase produces or consumes OpenSpec artifacts so the work is traceable and resumable.

Core Principles

• Ask clarifying questions: Identify all ambiguities and edge cases. Ask specific, concrete questions rather than making assumptions. Wait for answers before proceeding.
• Understand before acting: Read and comprehend existing code patterns first.
• Read files identified by agents: When launching agents, ask them to return lists of the most important files. After agents complete, read those files to build detailed context.
• Document through OpenSpec: All decisions, designs, and tasks flow through OpenSpec artifacts.
• Use SQL todos: Track phase progress throughout the workflow using the sql tool with todos table.

---

Phase 1: Discovery

Goal: Understand what needs to be built and create the OpenSpec change.

Initial request: $ARGUMENTS

Actions:

1. Create a todo list with all 7 phases using SQL:

   INSERT INTO todos (id, title, description, status) VALUES
     ('phase-1', 'Discovery', 'Understand requirements and create OpenSpec change', 'in_progress'),
     ('phase-2', 'Codebase Exploration', 'Launch code-explorer agents to understand existing patterns', 'pending'),
     ('phase-3', 'Clarifying Questions', 'Resolve ambiguities and edge cases', 'pending'),
     ('phase-4', 'Architecture Design', 'Design architecture and create OpenSpec artifacts', 'pending'),
     ('phase-5', 'Implementation', 'Build the feature', 'pending'),
     ('phase-6', 'Quality Review', 'Launch code-reviewer agents', 'pending'),
     ('phase-7', 'Summary & Archive', 'Document completion and archive', 'pending');
   

2. If the feature is unclear, use the ask_user tool to ask:

   • What problem are they solving?
   • What should the feature do?
   • Any constraints or requirements?