Mike Swanson
75ce1c2fd5
Enhanced code review and frontend validation with intelligent triggers: Code Review Agent Enhancement: - Added Sequential Thinking MCP integration for complex issues - Triggers on 2+ rejections or 3+ critical issues - New escalation format with root cause analysis - Comprehensive solution strategies with trade-off evaluation - Educational feedback to break rejection cycles - Files: .claude/agents/code-review.md (+308 lines) - Docs: CODE_REVIEW_ST_ENHANCEMENT.md, CODE_REVIEW_ST_TESTING.md Frontend Design Skill Enhancement: - Automatic invocation for ANY UI change - Comprehensive validation checklist (200+ checkpoints) - 8 validation categories (visual, interactive, responsive, a11y, etc.) - 3 validation levels (quick, standard, comprehensive) - Integration with code review workflow - Files: .claude/skills/frontend-design/SKILL.md (+120 lines) - Docs: UI_VALIDATION_CHECKLIST.md (462 lines), AUTOMATIC_VALIDATION_ENHANCEMENT.md (587 lines) Settings Optimization: - Repaired .claude/settings.local.json (fixed m365 pattern) - Reduced permissions from 49 to 33 (33% reduction) - Removed duplicates, sorted alphabetically - Created SETTINGS_PERMISSIONS.md documentation Checkpoint Command Enhancement: - Dual checkpoint system (git + database) - Saves session context to API for cross-machine recall - Includes git metadata in database context - Files: .claude/commands/checkpoint.md (+139 lines) Decision Rationale: - Sequential Thinking MCP breaks rejection cycles by identifying root causes - Automatic frontend validation catches UI issues before code review - Dual checkpoints enable complete project memory across machines - Settings optimization improves maintainability Total: 1,200+ lines of documentation and enhancements Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
569 lines
26 KiB
Plaintext
569 lines
26 KiB
Plaintext
1→<project_specification>
|
|
2→ <project_name>Auto-Claude-Plus</project_name>
|
|
3→
|
|
4→ <overview>
|
|
5→ Auto-Claude-Plus is an autonomous multi-agent coding framework that plans, builds, and validates software with minimal human intervention. It combines Auto-Claude's spec pipeline and multi-agent architecture, Ralph Wiggum's iterative persistence loop for difficult tasks, and the frontend-design skill's philosophy for producing distinctive, polished UIs. The system features a three-tier memory system (project, global, infrastructure), a Re-Spec capability for refining project vision mid-stream, and intelligent error recovery that continues work on non-blocking tasks while flagging issues for review.
|
|
6→ </overview>
|
|
7→
|
|
8→ <technology_stack>
|
|
9→ <frontend>
|
|
10→ <framework>Electron + React 18 + TypeScript</framework>
|
|
11→ <styling>Tailwind CSS + Custom Design System</styling>
|
|
12→ <state_management>Zustand (lightweight, scalable)</state_management>
|
|
13→ <ui_components>Radix UI primitives (accessible, unstyled)</ui_components>
|
|
14→ <bundler>Vite</bundler>
|
|
15→ </frontend>
|
|
16→ <backend>
|
|
17→ <runtime>Python 3.12+</runtime>
|
|
18→ <agent_sdk>Claude Agent SDK</agent_sdk>
|
|
19→ <database>SQLite (portable, Docker-friendly)</database>
|
|
20→ <orm>SQLAlchemy</orm>
|
|
21→ <api>FastAPI (for internal IPC and potential future REST API)</api>
|
|
22→ </backend>
|
|
23→ <communication>
|
|
24→ <api>IPC between Electron and Python backend</api>
|
|
25→ <realtime>WebSocket for agent terminal streaming</realtime>
|
|
26→ </communication>
|
|
27→ <deployment>
|
|
28→ <containerization>Docker + Docker Compose</containerization>
|
|
29→ <platforms>Windows, macOS, Linux</platforms>
|
|
30→ </deployment>
|
|
31→ </technology_stack>
|
|
32→
|
|
33→ <prerequisites>
|
|
34→ <environment_setup>
|
|
35→ - Python 3.12+ with uv package manager
|
|
36→ - Node.js 20+ with npm
|
|
37→ - Git
|
|
38→ - Docker (for containerized deployment)
|
|
39→ - Claude Pro/Max subscription
|
|
40→ - Claude Code CLI: npm install -g @anthropic-ai/claude-code
|
|
41→ </environment_setup>
|
|
42→ </prerequisites>
|
|
43→
|
|
44→ <feature_count>165</feature_count>
|
|
45→
|
|
46→ <security_and_access_control>
|
|
47→ <user_roles>
|
|
48→ <role name="owner">
|
|
49→ <permissions>
|
|
50→ - Full access to all features
|
|
51→ - Manage global and infrastructure memory
|
|
52→ - Configure deployment targets
|
|
53→ - Access all projects
|
|
54→ </permissions>
|
|
55→ <protected_routes>
|
|
56→ - All routes accessible
|
|
57→ </protected_routes>
|
|
58→ </role>
|
|
59→ </user_roles>
|
|
60→ <authentication>
|
|
61→ <method>Local only (no auth required for single-user internal use)</method>
|
|
62→ <session_timeout>none</session_timeout>
|
|
63→ <password_requirements>N/A</password_requirements>
|
|
64→ </authentication>
|
|
65→ <sensitive_operations>
|
|
66→ - Infrastructure memory contains server access info (stored locally only)
|
|
67→ - Git push operations require confirmation
|
|
68→ - Delete project requires confirmation
|
|
69→ </sensitive_operations>
|
|
70→ </security_and_access_control>
|
|
71→
|
|
72→ <core_features>
|
|
73→ <project_management>
|
|
74→ - Create new project with spec interview
|
|
75→ - Open/browse existing projects
|
|
76→ - Adopt existing codebase (import and run through spec interview)
|
|
77→ - Project dashboard with status overview
|
|
78→ - Project settings and configuration
|
|
79→ - Delete project with confirmation
|
|
80→ </project_management>
|
|
81→
|
|
82→ <spec_system>
|
|
83→ - Spec interview/creation wizard
|
|
84→ - Re-Spec feature (re-interview with existing context)
|
|
85→ - Automatic milestone detection for large projects
|
|
86→ - Re-Spec offered at milestones (MVP, phase completion)
|
|
87→ - Spec validation and completeness checking
|
|
88→ - Spec history and version tracking
|
|
89→ - Existing work re-evaluation against new spec
|
|
90→ </spec_system>
|
|
91→
|
|
92→ <kanban_board>
|
|
93→ - Visual task board with columns (Backlog, In Progress, QA, Done, Blocked)
|
|
94→ - Task cards with status, priority, agent assignment
|
|
95→ - Drag-and-drop task movement
|
|
96→ - Task filtering by status, agent, phase
|
|
97→ - Task details panel with full context
|
|
98→ - Phase grouping and visualization
|
|
99→ - Dependency visualization
|
|
100→ </kanban_board>
|
|
101→
|
|
102→ <agent_system>
|
|
103→ - Planner Agent (creates implementation plan)
|
|
104→ - Coder Agent (implements subtasks)
|
|
105→ - QA Reviewer Agent (validates acceptance criteria)
|
|
106→ - QA Fixer Agent (resolves issues)
|
|
107→ - Parallel agent execution (up to 12 terminals)
|
|
108→ - Agent terminals UI with live output streaming
|
|
109→ - Agent status indicators (idle, working, stuck, complete)
|
|
110→ - Subagent spawning for complex subtasks
|
|
111→ </agent_system>
|
|
112→
|
|
113→ <iterative_loop>
|
|
114→ - Single-pass validation (default mode)
|
|
115→ - Auto-escalation for failed tasks
|
|
116→ - Auto-escalation for detected complexity
|
|
117→ - Manual retry trigger
|
|
118→ - Ralph Wiggum mode (persistent iteration until completion)
|
|
119→ - Completion promise detection
|
|
120→ - Max iterations safety limit
|
|
121→ - Task flagging for multi-iteration mode
|
|
122→ </iterative_loop>
|
|
123→
|
|
124→ <memory_system>
|
|
125→ <project_memory>
|
|
126→ - Session insights (what worked, what failed)
|
|
127→ - Codebase map (what files do what)
|
|
128→ - Patterns discovered (coding conventions)
|
|
129→ - Gotchas (pitfalls to avoid)
|
|
130→ - Build progress history
|
|
131→ </project_memory>
|
|
132→ <global_memory>
|
|
133→ - User preferences (coding style, UI tastes)
|
|
134→ - Cross-project patterns
|
|
135→ - Common solutions ("last time I built auth...")
|
|
136→ - Technology preferences learned over time
|
|
137→ </global_memory>
|
|
138→ <infrastructure_memory>
|
|
139→ - Dev server locations and access methods
|
|
140→ - Docker server configurations
|
|
141→ - Deployment targets (local, cloud)
|
|
142→ - Database server connections
|
|
143→ - API key storage locations
|
|
144→ - Environment-specific configurations
|
|
145→ </infrastructure_memory>
|
|
146→ <memory_management>
|
|
147→ - Memory items tagged by project or global
|
|
148→ - Memory search and retrieval
|
|
149→ - Memory editing and cleanup
|
|
150→ - Memory import/export
|
|
151→ </memory_management>
|
|
152→ </memory_system>
|
|
153→
|
|
154→ <frontend_design_integration>
|
|
155→ - Design philosophy applied to all frontend projects
|
|
156→ - MVP mode (functional drafts acceptable)
|
|
157→ - Finished mode (frontend-design criteria required)
|
|
158→ - Opt-out via spec configuration
|
|
159→ - Design thinking framework (purpose, tone, constraints)
|
|
160→ - Typography, color, motion, spatial composition guidelines
|
|
161→ - Anti-pattern detection (generic AI slop)
|
|
162→ </frontend_design_integration>
|
|
163→
|
|
164→ <qa_and_testing>
|
|
165→ - Unit test generation for each component
|
|
166→ - E2E test generation at phase completion
|
|
167→ - Test execution against specified infrastructure
|
|
168→ - Test reporting with pass/fail details
|
|
169→ - Coverage tracking
|
|
170→ - QA loop (review -> fix -> re-review)
|
|
171→ - Infrastructure-aware testing (dev servers, Docker)
|
|
172→ </qa_and_testing>
|
|
173→
|
|
174→ <git_integration>
|
|
175→ - Git worktree isolation for safe development
|
|
176→ - Auto-commit per subtask completion
|
|
177→ - Auto-push on project/phase completion
|
|
178→ - Branch management (feature branches per spec)
|
|
179→ - Commit message generation
|
|
180→ - Git history visualization
|
|
181→ - Merge conflict detection
|
|
182→ </git_integration>
|
|
183→
|
|
184→ <progress_and_visibility>
|
|
185→ - Real-time notifications (task complete, fail, blocked)
|
|
186→ - Estimated time remaining per task/phase
|
|
187→ - Changelog generation from completed tasks
|
|
188→ - Build history and statistics
|
|
189→ - Agent activity timeline
|
|
190→ - Phase progress indicators
|
|
191→ - Overall project completion percentage
|
|
192→ </progress_and_visibility>
|
|
193→
|
|
194→ <error_handling>
|
|
195→ - Autonomous error recovery attempts
|
|
196→ - Task flagging for human review
|
|
197→ - Non-blocking continuation (work on other tasks)
|
|
198→ - Error categorization (recoverable, blocking, needs review)
|
|
199→ - Error history and patterns
|
|
200→ - Re-Spec suggestion for persistent issues
|
|
201→ </error_handling>
|
|
202→
|
|
203→ <deployment>
|
|
204→ - Docker containerization
|
|
205→ - Docker Compose configuration
|
|
206→ - Multi-machine access support
|
|
207→ - Infrastructure memory integration
|
|
208→ - Deployment pipeline generation
|
|
209→ - Environment configuration management
|
|
210→ </deployment>
|
|
211→
|
|
212→ <ui_ux>
|
|
213→ - Polished, distinctive interface (non-generic)
|
|
214→ - Dark/light theme support
|
|
215→ - Responsive layout (desktop-first, but usable on tablet)
|
|
216→ - Keyboard shortcuts for power users
|
|
217→ - Settings/preferences panel
|
|
218→ - Onboarding wizard for first-time setup
|
|
219→ </ui_ux>
|
|
220→ </core_features>
|
|
221→
|
|
222→ <database_schema>
|
|
223→ <tables>
|
|
224→ <projects>
|
|
225→ - id, name, description, path, status, created_at, updated_at
|
|
226→ - complexity (simple, medium, complex)
|
|
227→ - current_phase, total_phases
|
|
228→ - spec_version, last_respec_at
|
|
229→ </projects>
|
|
230→ <specs>
|
|
231→ - id, project_id, version, content, created_at
|
|
232→ - is_active, parent_spec_id (for Re-Spec tracking)
|
|
233→ </specs>
|
|
234→ <tasks>
|
|
235→ - id, project_id, spec_id, phase_id, name, description
|
|
236→ - status (backlog, in_progress, qa, done, blocked)
|
|
237→ - priority, estimated_time, actual_time
|
|
238→ - agent_type, iteration_count, flagged_for_review
|
|
239→ - depends_on (JSON array of task IDs)
|
|
240→ </tasks>
|
|
241→ <phases>
|
|
242→ - id, project_id, name, order, status
|
|
243→ - depends_on (JSON array of phase IDs)
|
|
244→ - milestone_type (none, mvp, release)
|
|
245→ </phases>
|
|
246→ <agent_sessions>
|
|
247→ - id, project_id, task_id, agent_type
|
|
248→ - started_at, ended_at, status, output_log
|
|
249→ - iterations, completion_promise
|
|
250→ </agent_sessions>
|
|
251→ <memory_project>
|
|
252→ - id, project_id, type (insight, pattern, gotcha, codebase_map)
|
|
253→ - content, metadata, created_at
|
|
254→ </memory_project>
|
|
255→ <memory_global>
|
|
256→ - id, type (preference, pattern, solution)
|
|
257→ - content, metadata, created_at, usage_count
|
|
258→ </memory_global>
|
|
259→ <memory_infrastructure>
|
|
260→ - id, name, type (server, docker, database, deployment)
|
|
261→ - config (JSON), projects (JSON array of project IDs or null for all)
|
|
262→ - created_at, updated_at
|
|
263→ </memory_infrastructure>
|
|
264→ <notifications>
|
|
265→ - id, project_id, type, message, read, created_at
|
|
266→ </notifications>
|
|
267→ <settings>
|
|
268→ - id, key, value, updated_at
|
|
269→ </settings>
|
|
270→ </tables>
|
|
271→ </database_schema>
|
|
272→
|
|
273→ <api_endpoints_summary>
|
|
274→ <projects>
|
|
275→ - GET /api/projects - List all projects
|
|
276→ - POST /api/projects - Create new project
|
|
277→ - GET /api/projects/:id - Get project details
|
|
278→ - PUT /api/projects/:id - Update project
|
|
279→ - DELETE /api/projects/:id - Delete project
|
|
280→ - POST /api/projects/:id/adopt - Adopt existing codebase
|
|
281→ </projects>
|
|
282→ <specs>
|
|
283→ - GET /api/projects/:id/spec - Get current spec
|
|
284→ - POST /api/projects/:id/spec - Create/update spec
|
|
285→ - POST /api/projects/:id/respec - Trigger Re-Spec
|
|
286→ - GET /api/projects/:id/spec/history - Get spec versions
|
|
287→ </specs>
|
|
288→ <tasks>
|
|
289→ - GET /api/projects/:id/tasks - List tasks (with filters)
|
|
290→ - POST /api/projects/:id/tasks - Create task
|
|
291→ - PUT /api/tasks/:id - Update task
|
|
292→ - PUT /api/tasks/:id/status - Update task status
|
|
293→ - POST /api/tasks/:id/retry - Retry task
|
|
294→ - POST /api/tasks/:id/flag - Flag for review
|
|
295→ </tasks>
|
|
296→ <agents>
|
|
297→ - POST /api/agents/start - Start agent session
|
|
298→ - POST /api/agents/:id/stop - Stop agent session
|
|
299→ - GET /api/agents/active - List active agents
|
|
300→ - WS /api/agents/:id/stream - Stream agent output
|
|
301→ </agents>
|
|
302→ <memory>
|
|
303→ - GET /api/memory/project/:id - Get project memory
|
|
304→ - POST /api/memory/project/:id - Add project memory
|
|
305→ - GET /api/memory/global - Get global memory
|
|
306→ - POST /api/memory/global - Add global memory
|
|
307→ - GET /api/memory/infrastructure - Get infrastructure memory
|
|
308→ - POST /api/memory/infrastructure - Add infrastructure config
|
|
309→ - PUT /api/memory/infrastructure/:id - Update infrastructure config
|
|
310→ </memory>
|
|
311→ <notifications>
|
|
312→ - GET /api/notifications - Get notifications
|
|
313→ - PUT /api/notifications/:id/read - Mark as read
|
|
314→ - DELETE /api/notifications/:id - Delete notification
|
|
315→ </notifications>
|
|
316→ <settings>
|
|
317→ - GET /api/settings - Get all settings
|
|
318→ - PUT /api/settings - Update settings
|
|
319→ </settings>
|
|
320→ </api_endpoints_summary>
|
|
321→
|
|
322→ <ui_layout>
|
|
323→ <main_structure>
|
|
324→ - Left sidebar: Project list, navigation, quick actions
|
|
325→ - Main content area: Context-dependent (kanban, terminals, settings, etc.)
|
|
326→ - Right panel (collapsible): Task details, agent output, memory viewer
|
|
327→ - Top bar: Project name, phase indicator, notifications, settings
|
|
328→ - Bottom bar: Agent status summary, progress indicator
|
|
329→ </main_structure>
|
|
330→ <key_screens>
|
|
331→ - Dashboard: Project overview, recent activity, quick stats
|
|
332→ - Kanban Board: Visual task management
|
|
333→ - Agent Terminals: Live agent output with multiple terminals
|
|
334→ - Spec Editor: View/edit current spec, trigger Re-Spec
|
|
335→ - Memory Manager: Browse/edit all memory types
|
|
336→ - Infrastructure Config: Manage servers, Docker, deployment targets
|
|
337→ - Settings: App preferences, theme, shortcuts
|
|
338→ - Project Creation Wizard: New project setup flow
|
|
339→ - Re-Spec Interview: Guided re-interview with context
|
|
340→ </key_screens>
|
|
341→ </ui_layout>
|
|
342→
|
|
343→ <design_system>
|
|
344→ <philosophy>
|
|
345→ - Distinctive, professional interface (not generic AI slop)
|
|
346→ - Clean but not sterile - subtle personality
|
|
347→ - Information-dense but not overwhelming
|
|
348→ - Emphasize clarity and readability for long coding sessions
|
|
349→ </philosophy>
|
|
350→ <color_palette>
|
|
351→ - Primary: Deep blue (#1a365d) - trust, focus
|
|
352→ - Accent: Vibrant teal (#0d9488) - action, success
|
|
353→ - Warning: Amber (#f59e0b) - attention
|
|
354→ - Error: Rose (#e11d48) - problems
|
|
355→ - Background: Slate gray tones (dark mode default)
|
|
356→ - Text: High contrast for readability
|
|
357→ </color_palette>
|
|
358→ <typography>
|
|
359→ - Headings: Inter or similar geometric sans-serif
|
|
360→ - Body: System font stack for performance
|
|
361→ - Code: JetBrains Mono or Fira Code (monospace with ligatures)
|
|
362→ </typography>
|
|
363→ <motion>
|
|
364→ - Subtle transitions (150-300ms)
|
|
365→ - Meaningful animations (task completion, agent status changes)
|
|
366→ - No gratuitous motion - respect user focus
|
|
367→ </motion>
|
|
368→ </design_system>
|
|
369→
|
|
370→ <implementation_steps>
|
|
371→ <step number="1">
|
|
372→ <title>Foundation & Infrastructure</title>
|
|
373→ <tasks>
|
|
374→ - Set up Electron + React + TypeScript project structure
|
|
375→ - Configure Vite bundler and Tailwind CSS
|
|
376→ - Set up Python backend with FastAPI
|
|
377→ - Configure SQLite database with SQLAlchemy
|
|
378→ - Implement IPC bridge between Electron and Python
|
|
379→ - Create Docker configuration
|
|
380→ </tasks>
|
|
381→ </step>
|
|
382→ <step number="2">
|
|
383→ <title>Core Data Layer</title>
|
|
384→ <tasks>
|
|
385→ - Implement database schema and migrations
|
|
386→ - Create Python models for all entities
|
|
387→ - Build CRUD API endpoints for projects, specs, tasks
|
|
388→ - Implement basic memory storage (all three types)
|
|
389→ - Set up WebSocket for real-time updates
|
|
390→ </tasks>
|
|
391→ </step>
|
|
392→ <step number="3">
|
|
393→ <title>Spec System</title>
|
|
394→ <tasks>
|
|
395→ - Build spec interview wizard UI
|
|
396→ - Implement spec creation flow
|
|
397→ - Build Re-Spec interview with existing context
|
|
398→ - Implement spec versioning and history
|
|
399→ - Add milestone detection logic
|
|
400→ - Build spec validation
|
|
401→ </tasks>
|
|
402→ </step>
|
|
403→ <step number="4">
|
|
404→ <title>Agent System</title>
|
|
405→ <tasks>
|
|
406→ - Integrate Claude Agent SDK
|
|
407→ - Implement Planner Agent
|
|
408→ - Implement Coder Agent
|
|
409→ - Implement QA Reviewer Agent
|
|
410→ - Implement QA Fixer Agent
|
|
411→ - Build agent session management
|
|
412→ - Implement parallel agent execution
|
|
413→ </tasks>
|
|
414→ </step>
|
|
415→ <step number="5">
|
|
416→ <title>Iterative Loop Integration</title>
|
|
417→ <tasks>
|
|
418→ - Implement single-pass validation
|
|
419→ - Build auto-escalation detection
|
|
420→ - Implement Ralph Wiggum mode
|
|
421→ - Add completion promise detection
|
|
422→ - Build task flagging system
|
|
423→ - Implement retry logic
|
|
424→ </tasks>
|
|
425→ </step>
|
|
426→ <step number="6">
|
|
427→ <title>Kanban Board & Task Management</title>
|
|
428→ <tasks>
|
|
429→ - Build kanban board UI with drag-and-drop
|
|
430→ - Implement task cards with status
|
|
431→ - Add filtering and sorting
|
|
432→ - Build task details panel
|
|
433→ - Implement phase grouping
|
|
434→ - Add dependency visualization
|
|
435→ </tasks>
|
|
436→ </step>
|
|
437→ <step number="7">
|
|
438→ <title>Agent Terminals UI</title>
|
|
439→ <tasks>
|
|
440→ - Build terminal component with live streaming
|
|
441→ - Implement multi-terminal layout
|
|
442→ - Add agent status indicators
|
|
443→ - Build terminal history/scrollback
|
|
444→ - Implement terminal controls (pause, clear, copy)
|
|
445→ </tasks>
|
|
446→ </step>
|
|
447→ <step number="8">
|
|
448→ <title>Memory System</title>
|
|
449→ <tasks>
|
|
450→ - Build memory manager UI
|
|
451→ - Implement project memory CRUD
|
|
452→ - Implement global memory with cross-project access
|
|
453→ - Build infrastructure memory management
|
|
454→ - Add memory search and tagging
|
|
455→ - Implement memory learning/inference
|
|
456→ </tasks>
|
|
457→ </step>
|
|
458→ <step number="9">
|
|
459→ <title>Git Integration</title>
|
|
460→ <tasks>
|
|
461→ - Implement git worktree management
|
|
462→ - Build auto-commit logic
|
|
463→ - Implement auto-push on completion
|
|
464→ - Add branch management UI
|
|
465→ - Build commit history visualization
|
|
466→ </tasks>
|
|
467→ </step>
|
|
468→ <step number="10">
|
|
469→ <title>QA & Testing System</title>
|
|
470→ <tasks>
|
|
471→ - Implement unit test generation
|
|
472→ - Build E2E test generation
|
|
473→ - Integrate with infrastructure memory for test targets
|
|
474→ - Build test execution and reporting
|
|
475→ - Implement QA loop (review -> fix -> re-review)
|
|
476→ </tasks>
|
|
477→ </step>
|
|
478→ <step number="11">
|
|
479→ <title>Frontend Design Integration</title>
|
|
480→ <tasks>
|
|
481→ - Integrate design philosophy guidelines
|
|
482→ - Build MVP vs Finished mode detection
|
|
483→ - Implement design validation checks
|
|
484→ - Add anti-pattern detection
|
|
485→ </tasks>
|
|
486→ </step>
|
|
487→ <step number="12">
|
|
488→ <title>Progress & Notifications</title>
|
|
489→ <tasks>
|
|
490→ - Build notification system
|
|
491→ - Implement time estimation
|
|
492→ - Build changelog generation
|
|
493→ - Add progress indicators throughout UI
|
|
494→ - Build activity timeline
|
|
495→ </tasks>
|
|
496→ </step>
|
|
497→ <step number="13">
|
|
498→ <title>Error Handling & Recovery</title>
|
|
499→ <tasks>
|
|
500→ - Implement autonomous recovery logic
|
|
501→ - Build task flagging for review
|
|
502→ - Implement non-blocking continuation
|
|
503→ - Add error categorization
|
|
504→ - Build Re-Spec suggestion for persistent issues
|
|
505→ </tasks>
|
|
506→ </step>
|
|
507→ <step number="14">
|
|
508→ <title>Polish & Design System</title>
|
|
509→ <tasks>
|
|
510→ - Apply design system throughout
|
|
511→ - Implement dark/light themes
|
|
512→ - Add keyboard shortcuts
|
|
513→ - Build onboarding wizard
|
|
514→ - Refine animations and transitions
|
|
515→ - Ensure responsive layout
|
|
516→ </tasks>
|
|
517→ </step>
|
|
518→ <step number="15">
|
|
519→ <title>Deployment & Documentation</title>
|
|
520→ <tasks>
|
|
521→ - Finalize Docker configuration
|
|
522→ - Build deployment pipeline support
|
|
523→ - Create user documentation
|
|
524→ - Add in-app help system
|
|
525→ - Final testing and bug fixes
|
|
526→ </tasks>
|
|
527→ </step>
|
|
528→ </implementation_steps>
|
|
529→
|
|
530→ <success_criteria>
|
|
531→ <functionality>
|
|
532→ - Can create a new project through spec interview
|
|
533→ - Can adopt existing codebase and run through spec
|
|
534→ - Re-Spec works with full context awareness
|
|
535→ - Agents execute tasks autonomously
|
|
536→ - Iterative loop handles difficult tasks
|
|
537→ - Memory persists and informs across sessions
|
|
538→ - Git operations work correctly (worktree, commit, push)
|
|
539→ - QA loop validates and fixes issues
|
|
540→ </functionality>
|
|
541→ <user_experience>
|
|
542→ - Kanban board is intuitive and responsive
|
|
543→ - Agent terminals provide clear visibility
|
|
544→ - Notifications keep user informed
|
|
545→ - Progress is always visible
|
|
546→ - Error states are clear and actionable
|
|
547→ </user_experience>
|
|
548→ <technical_quality>
|
|
549→ - No mock data - all real persistence
|
|
550→ - Unit tests for core functionality
|
|
551→ - E2E tests for critical workflows
|
|
552→ - Clean error handling throughout
|
|
553→ - Performance acceptable with many tasks
|
|
554→ </technical_quality>
|
|
555→ <design_polish>
|
|
556→ - UI follows design system consistently
|
|
557→ - Dark mode is fully implemented
|
|
558→ - No generic "AI slop" aesthetics
|
|
559→ - Animations are subtle and meaningful
|
|
560→ - Typography is readable for long sessions
|
|
561→ </design_polish>
|
|
562→ </success_criteria>
|
|
563→</project_specification>
|
|
564→
|
|
|
|
<system-reminder>
|
|
Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.
|
|
</system-reminder>
|