# Plan Tab UX Refactor: Shift from Tasks to Features

## The Problem
The current "Plan" tab in the Vibn Dashboard relies on a granular "Tasks" model (e.g., "Set up database", "Fix padding"). 
This model fails for two reasons:
1. **User Experience:** Non-technical founders do not think in atomic engineering tasks. They think in deliverables and capabilities.
2. **AI Autonomy:** When the AI is delegated a low-level task, it lacks the broader context required to make intelligent architectural decisions. If it hits an error, it doesn't know the overarching goal well enough to pivot successfully.

## The Solution: The "Feature-Driven" Methodology
To successfully adapt the "Spec Kit" methodology into a seamless, founder-friendly UI, we must elevate the execution model from "Tasks" to "Features".

A Feature is a tangible, independently testable slice of value (e.g., *Authentication*, *User Profiles*, *Stripe Checkout*).

### The New Plan Hierarchy
The Plan tab will be restructured into three distinct, interconnected pillars that guide the AI from concept to deployment:

#### 1. Objective (The "Why")
*   **What it is:** The North Star. It defines the product vision, the target audience, and the overall goal.
*   **AI Usage:** The AI reads the Objective on every turn to ensure its design, tone, and technical architecture align with the user's ultimate goal.

#### 2. Features (The "What" — *Replacing Tasks*)
*   **What it is:** The high-level product roadmap. 
*   **Example Items:** `Landing Page`, `User Dashboard`, `Payment Integration`.
*   **AI Usage:** This is the primary unit of delegation. When a user clicks **"Delegate to AI"**, they are delegating an entire Feature. The AI takes this broad scope, breaks it down into an internal, invisible checklist of atomic technical tasks (using the Spec Kit methodology), and executes them asynchronously.

#### 3. Architecture & Decisions (The "How")
*   **What it is:** The log of technical choices (e.g., `Database: Postgres`, `Auth: NextAuth`, `UI: Tailwind`).
*   **AI Usage:** Before writing code for a Feature, the AI cross-references this log to ensure consistency across the codebase.

## Execution Flow (The "Tony Stark" Experience)
1. **Architect Mode:** The user collaborates with the AI to brainstorm the app. The AI automatically populates the **Objective**, logs the **Architecture**, and generates a roadmap of **Features**.
2. **Delegate Mode:** The user selects the first Feature (e.g., "Authentication") and clicks "Delegate". 
3. **Headless Execution:** The background `vibn-agent-runner` takes over. It reads the Objective, respects the Architecture, breaks the Feature into atomic tasks, codes them, verifies them with headless browser testing, and ships the completed Feature to production.

This shift abstracts away the bureaucratic boilerplate of traditional software engineering (Jira tickets, PRDs, Markdown specs) and replaces it with a simple, high-leverage UI that empowers non-technical founders to operate as Product Managers guiding an autonomous engineering team.
