@arvorco/relentless 0.1.0 → 0.1.6

package/.claude/skills/plan/SKILL.md

@@ -1,179 +0,0 @@
----
-name: plan
-description: "Generate technical implementation plan from feature specification. Use after creating spec. Triggers on: create plan, technical plan, implementation design."
----
-
-# Technical Implementation Plan Generator
-
-Create detailed technical plans that translate feature specifications into implementation designs.
-
----
-
-## The Job
-
-1. Read the feature specification (`spec.md`)
-2. Read project constitution for technical constraints
-3. Generate technical architecture and implementation plan
-4. Save to `plan.md` in the feature directory
-
----
-
-## Step 1: Locate Feature Files
-
-Find the current feature directory:
-- Look in `relentless/features/` for the most recent feature
-- Or ask user which feature to plan
-- Verify `spec.md` exists
-
----
-
-## Step 2: Load Context
-
-Read these files:
-1. **relentless/constitution.md** - Project governance and technical standards
-2. **relentless/features/NNN-feature/spec.md** - Feature requirements
-3. Project README or docs for tech stack information
-
----
-
-## Step 3: Generate Technical Plan
-
-Using the template at `templates/plan-template.md`, create a plan with:
-
-### Required Sections:
-
-**1. Technical Overview**
-- Architecture approach
-- Key technologies to use (from constitution/existing stack)
-- Integration points
-
-**2. Data Models**
-- Database schemas
-- Entity relationships
-- Field definitions with types
-- Indexes and constraints
-
-**3. API Contracts**
-- Endpoints and methods
-- Request/response formats
-- Authentication requirements
-- Error responses
-
-**4. Implementation Strategy**
-- Phase breakdown
-- Dependencies between components
-- Integration approach
-
-**5. Testing Strategy**
-- Unit test approach
-- Integration test scenarios
-- E2E test cases
-- Test data requirements
-
-**6. Security Considerations**
-- Authentication/authorization
-- Data validation
-- Security best practices
-- Compliance requirements
-
-**7. Rollout Plan**
-- Deployment strategy
-- Migration requirements (if any)
-- Monitoring and observability
-- Rollback plan
-
----
-
-## Step 4: Ensure Constitution Compliance
-
-Validate the plan against constitution:
-- **MUST** rules: Required, plan must follow these
-- **SHOULD** rules: Best practices, document any deviations
-
-If plan violates MUST rules, revise until compliant.
-
----
-
-## Step 5: Save & Report
-
-1. Save plan to `relentless/features/NNN-feature/plan.md`
-2. Update progress.txt with plan creation timestamp
-3. Report:
-   - Plan location
-   - Key technical decisions
-   - Constitution compliance: PASS/FAIL
-   - Next step: `/relentless.tasks`
-
----
-
-## Example Sections
-
-```markdown
-# Technical Implementation Plan: User Authentication
-
-## Technical Overview
-
-**Architecture:** Three-tier (API, Service, Data)
-**Stack:** Node.js, TypeScript, PostgreSQL
-**Authentication:** JWT tokens with refresh mechanism
-
-## Data Models
-
-### User Table
-\`\`\`sql
-CREATE TABLE users (
-  id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-  email VARCHAR(255) UNIQUE NOT NULL,
-  password_hash VARCHAR(255) NOT NULL,
-  confirmed BOOLEAN DEFAULT FALSE,
-  created_at TIMESTAMP DEFAULT NOW(),
-  updated_at TIMESTAMP DEFAULT NOW()
-);
-
-CREATE INDEX idx_users_email ON users(email);
-\`\`\`
-
-## API Contracts
-
-### POST /api/auth/register
-**Request:**
-\`\`\`json
-{
-  "email": "user@example.com",
-  "password": "password123"
-}
-\`\`\`
-
-**Response (201):**
-\`\`\`json
-{
-  "id": "uuid",
-  "email": "user@example.com",
-  "message": "Confirmation email sent"
-}
-\`\`\`
-
-## Testing Strategy
-
-**Unit Tests:**
-- Password hashing utility
-- Email validation
-- Token generation/verification
-
-**Integration Tests:**
-- Full registration flow
-- Email sending
-- Database operations
-
-**E2E Tests:**
-- Complete user journey from signup to login
-```
-
----
-
-## Notes
-
-- Plan bridges WHAT (spec) to HOW (implementation)
-- Include specific technologies and patterns
-- Must comply with constitution
-- Detailed enough for task generation

package/.claude/skills/plan/templates/plan-template.md

@@ -1,104 +0,0 @@
-# Implementation Plan: [FEATURE]
-
-**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
-**Input**: Feature specification from `/specs/[###-feature-name]/spec.md`
-
-**Note**: This template is filled in by the `/relentless.plan` command. See `.specify/templates/commands/plan.md` for the execution workflow.
-
-## Summary
-
-[Extract from feature spec: primary requirement + technical approach from research]
-
-## Technical Context
-
-<!--
-  ACTION REQUIRED: Replace the content in this section with the technical details
-  for the project. The structure here is presented in advisory capacity to guide
-  the iteration process.
--->
-
-**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]  
-**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]  
-**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]  
-**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]  
-**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
-**Project Type**: [single/web/mobile - determines source structure]  
-**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]  
-**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]  
-**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]
-
-## Constitution Check
-
-*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
-
-[Gates determined based on constitution file]
-
-## Project Structure
-
-### Documentation (this feature)
-
-```text
-specs/[###-feature]/
-├── plan.md              # This file (/relentless.plan command output)
-├── research.md          # Phase 0 output (/relentless.plan command)
-├── data-model.md        # Phase 1 output (/relentless.plan command)
-├── quickstart.md        # Phase 1 output (/relentless.plan command)
-├── contracts/           # Phase 1 output (/relentless.plan command)
-└── tasks.md             # Phase 2 output (/relentless.tasks command - NOT created by /relentless.plan)
-```
-
-### Source Code (repository root)
-<!--
-  ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
-  for this feature. Delete unused options and expand the chosen structure with
-  real paths (e.g., apps/admin, packages/something). The delivered plan must
-  not include Option labels.
--->
-
-```text
-# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
-src/
-├── models/
-├── services/
-├── cli/
-└── lib/
-
-tests/
-├── contract/
-├── integration/
-└── unit/
-
-# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
-backend/
-├── src/
-│   ├── models/
-│   ├── services/
-│   └── api/
-└── tests/
-
-frontend/
-├── src/
-│   ├── components/
-│   ├── pages/
-│   └── services/
-└── tests/
-
-# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
-api/
-└── [same as backend above]
-
-ios/ or android/
-└── [platform-specific structure: feature modules, UI flows, platform tests]
-```
-
-**Structure Decision**: [Document the selected structure and reference the real
-directories captured above]
-
-## Complexity Tracking
-
-> **Fill ONLY if Constitution Check has violations that must be justified**
-
-| Violation | Why Needed | Simpler Alternative Rejected Because |
-|-----------|------------|-------------------------------------|
-| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
-| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |

package/.claude/skills/prd/SKILL.md

@@ -1,242 +0,0 @@
----
-name: prd
-description: "Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out."
----
-
-# PRD Generator
-
-Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.
-
----
-
-## The Job
-
-1. Receive a feature description from the user
-2. Ask 3-5 essential clarifying questions (with lettered options)
-3. Generate a structured PRD based on answers
-4. Save to `relentless/features/[feature-name]/prd.md`
-
-**Important:** Do NOT start implementing. Just create the PRD.
-
----
-
-## Step 1: Clarifying Questions
-
-Ask only critical questions where the initial prompt is ambiguous. Focus on:
-
-- **Problem/Goal:** What problem does this solve?
-- **Core Functionality:** What are the key actions?
-- **Scope/Boundaries:** What should it NOT do?
-- **Success Criteria:** How do we know it's done?
-
-### Format Questions Like This:
-
-```
-1. What is the primary goal of this feature?
-   A. Improve user onboarding experience
-   B. Increase user retention
-   C. Reduce support burden
-   D. Other: [please specify]
-
-2. Who is the target user?
-   A. New users only
-   B. Existing users only
-   C. All users
-   D. Admin users only
-
-3. What is the scope?
-   A. Minimal viable version
-   B. Full-featured implementation
-   C. Just the backend/API
-   D. Just the UI
-```
-
-This lets users respond with "1A, 2C, 3B" for quick iteration.
-
----
-
-## Step 2: PRD Structure
-
-Generate the PRD with these sections:
-
-### 1. Introduction/Overview
-Brief description of the feature and the problem it solves.
-
-### 2. Goals
-Specific, measurable objectives (bullet list).
-
-### 3. User Stories
-Each story needs:
-- **Title:** Short descriptive name
-- **Description:** "As a [user], I want [feature] so that [benefit]"
-- **Acceptance Criteria:** Verifiable checklist of what "done" means
-
-Each story should be small enough to implement in one focused session.
-
-**Format:**
-```markdown
-### US-001: [Title]
-**Description:** As a [user], I want [feature] so that [benefit].
-
-**Acceptance Criteria:**
-- [ ] Specific verifiable criterion
-- [ ] Another criterion
-- [ ] Typecheck/lint passes
-- [ ] **[UI stories only]** Verify in browser using dev-browser skill
-```
-
-**Important:** 
-- Acceptance criteria must be verifiable, not vague. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good.
-- **For any story with UI changes:** Always include "Verify in browser using dev-browser skill" as acceptance criteria. This ensures visual verification of frontend work.
-
-### 4. Functional Requirements
-Numbered list of specific functionalities:
-- "FR-1: The system must allow users to..."
-- "FR-2: When a user clicks X, the system must..."
-
-Be explicit and unambiguous.
-
-### 5. Non-Goals (Out of Scope)
-What this feature will NOT include. Critical for managing scope.
-
-### 6. Design Considerations (Optional)
-- UI/UX requirements
-- Link to mockups if available
-- Relevant existing components to reuse
-
-### 7. Technical Considerations (Optional)
-- Known constraints or dependencies
-- Integration points with existing systems
-- Performance requirements
-
-### 8. Success Metrics
-How will success be measured?
-- "Reduce time to complete X by 50%"
-- "Increase conversion rate by 10%"
-
-### 9. Open Questions
-Remaining questions or areas needing clarification.
-
----
-
-## Writing for Junior Developers
-
-The PRD reader may be a junior developer or AI agent. Therefore:
-
-- Be explicit and unambiguous
-- Avoid jargon or explain it
-- Provide enough detail to understand purpose and core logic
-- Number requirements for easy reference
-- Use concrete examples where helpful
-
----
-
-## Output
-
-- **Format:** Markdown (`.md`)
-- **Location:** `relentless/features/[feature-name]/`
-- **Filename:** `prd.md`
-
-**Note:** Create the feature directory first if it doesn't exist: `mkdir -p relentless/features/[feature-name]`
-
----
-
-## Example PRD
-
-```markdown
-# PRD: Task Priority System
-
-## Introduction
-
-Add priority levels to tasks so users can focus on what matters most. Tasks can be marked as high, medium, or low priority, with visual indicators and filtering to help users manage their workload effectively.
-
-## Goals
-
-- Allow assigning priority (high/medium/low) to any task
-- Provide clear visual differentiation between priority levels
-- Enable filtering and sorting by priority
-- Default new tasks to medium priority
-
-## User Stories
-
-### US-001: Add priority field to database
-**Description:** As a developer, I need to store task priority so it persists across sessions.
-
-**Acceptance Criteria:**
-- [ ] Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
-- [ ] Generate and run migration successfully
-- [ ] Typecheck passes
-
-### US-002: Display priority indicator on task cards
-**Description:** As a user, I want to see task priority at a glance so I know what needs attention first.
-
-**Acceptance Criteria:**
-- [ ] Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
-- [ ] Priority visible without hovering or clicking
-- [ ] Typecheck passes
-- [ ] Verify in browser using dev-browser skill
-
-### US-003: Add priority selector to task edit
-**Description:** As a user, I want to change a task's priority when editing it.
-
-**Acceptance Criteria:**
-- [ ] Priority dropdown in task edit modal
-- [ ] Shows current priority as selected
-- [ ] Saves immediately on selection change
-- [ ] Typecheck passes
-- [ ] Verify in browser using dev-browser skill
-
-### US-004: Filter tasks by priority
-**Description:** As a user, I want to filter the task list to see only high-priority items when I'm focused.
-
-**Acceptance Criteria:**
-- [ ] Filter dropdown with options: All | High | Medium | Low
-- [ ] Filter persists in URL params
-- [ ] Empty state message when no tasks match filter
-- [ ] Typecheck passes
-- [ ] Verify in browser using dev-browser skill
-
-## Functional Requirements
-
-- FR-1: Add `priority` field to tasks table ('high' | 'medium' | 'low', default 'medium')
-- FR-2: Display colored priority badge on each task card
-- FR-3: Include priority selector in task edit modal
-- FR-4: Add priority filter dropdown to task list header
-- FR-5: Sort by priority within each status column (high to medium to low)
-
-## Non-Goals
-
-- No priority-based notifications or reminders
-- No automatic priority assignment based on due date
-- No priority inheritance for subtasks
-
-## Technical Considerations
-
-- Reuse existing badge component with color variants
-- Filter state managed via URL search params
-- Priority stored in database, not computed
-
-## Success Metrics
-
-- Users can change priority in under 2 clicks
-- High-priority tasks immediately visible at top of lists
-- No regression in task list performance
-
-## Open Questions
-
-- Should priority affect task ordering within a column?
-- Should we add keyboard shortcuts for priority changes?
-```
-
----
-
-## Checklist
-
-Before saving the PRD:
-
-- [ ] Asked clarifying questions with lettered options
-- [ ] Incorporated user's answers
-- [ ] User stories are small and specific
-- [ ] Functional requirements are numbered and unambiguous
-- [ ] Non-goals section defines clear boundaries
-- [ ] Saved to `relentless/features/[feature-name]/prd.md`