@arvorco/relentless 0.1.0 → 0.1.6

package/README.md

@@ -20,6 +20,10 @@
 **For Claude Code, Amp, or OpenCode users** (Recommended - Full Skills Support):
 ```bash
 # 1. Install Relentless globally
+npm install -g @arvorco/relentless
+# or with bun
+bun install -g @arvorco/relentless
+# or directly from GitHub
 bun install -g github:ArvorCo/Relentless
 
 # 2. Initialize in your project
@@ -45,7 +49,9 @@ relentless run --feature 003-user-auth --tui
 **For Droid, Codex, or other agents** (Manual Workflow):
 ```bash
 # 1. Install and initialize
-bun install -g github:ArvorCo/Relentless
+npm install -g @arvorco/relentless
+# or
+bun install -g @arvorco/relentless
 cd your-project
 relentless init
 
@@ -158,35 +164,46 @@ Five specialized skills for Claude Code, Amp, and other AI agents:
 
 ### Prerequisites
 
-- [Bun](https://bun.sh) runtime
+- [Bun](https://bun.sh) runtime (recommended) or Node.js 20+
 - At least one AI coding agent installed (Claude Code, Amp, etc.)
 
 ```bash
-# Install Bun (if needed)
+# Install Bun (recommended)
 curl -fsSL https://bun.sh/install | bash
 ```
 
-### Option 1: Clone the Repository (Recommended)
+### Option 1: Install from npm (Recommended)
 
 ```bash
-git clone https://github.com/ArvorCo/Relentless.git
-cd Relentless
-bun install
+# Using npm
+npm install -g @arvorco/relentless
+
+# Using bun (faster)
+bun install -g @arvorco/relentless
+
+# Using bunx (no installation)
+bunx @arvorco/relentless init
 ```
 
-### Option 2: Install Globally
+### Option 2: Install from GitHub
 
 ```bash
+# Latest stable release
 bun install -g github:ArvorCo/Relentless
 
-# Or install from npm when published
-bun install -g relentless
+# Or run directly
+bunx github:ArvorCo/Relentless init
 ```
 
-### Option 3: Run with bunx (No Installation)
+### Option 3: Clone for Development
 
 ```bash
-bunx github:ArvorCo/Relentless init
+git clone https://github.com/ArvorCo/Relentless.git
+cd Relentless
+bun install
+
+# Run locally
+bun run bin/relentless.ts --help
 ```
 
 ---
@@ -398,7 +415,7 @@ Support through extensions or alternative mechanisms:
 |-------|---------|--------|
 | **Gemini** | `gemini` | 🔄 Extensions (see below) |
 
-**Gemini Setup:** See [GEMINI_SETUP.md](./GEMINI_SETUP.md) for extensions integration guide.
+**Gemini Setup:** See [docs/GEMINI_SETUP.md](./docs/GEMINI_SETUP.md) for extensions integration guide.
 
 ### Tier 3: Manual/CLI Workflow
 

package/bin/relentless.ts

@@ -179,9 +179,9 @@ program
       const checklistPath = join(featureDir, "checklist.md");
       if (existsSync(checklistPath)) {
         console.log(chalk.dim("  Merging checklist.md criteria..."));
-        const checklistContent = await Bun.file(checklistPath).text();
         // TODO: Parse checklist and merge into acceptance criteria
         // For now, just note that it exists
+        // const checklistContent = await Bun.file(checklistPath).text();
       }
     }
 

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "@arvorco/relentless",
-  "version": "0.1.0",
+  "version": "0.1.6",
   "description": "Universal AI agent orchestrator - works with Claude Code, Amp, OpenCode, Codex, Droid, and Gemini",
   "type": "module",
   "publishConfig": {
     "access": "public"
   },
   "bin": {
-    "relentless": "./bin/relentless.ts"
+    "relentless": "bin/relentless.ts"
   },
   "scripts": {
     "start": "bun run bin/relentless.ts",
@@ -17,6 +17,7 @@
     "test": "bun test"
   },
   "dependencies": {
+    "@arvorco/relentless": "^0.1.0",
     "chalk": "^5.3.0",
     "commander": "^12.1.0",
     "figures": "^6.0.0",

package/.claude/commands/relentless.plan.old.md

@@ -1,89 +0,0 @@
----
-description: Execute the implementation planning workflow using the plan template to generate design artifacts.
-handoffs: 
-  - label: Create Tasks
-    agent: relentless.tasks
-    prompt: Break the plan into tasks
-    send: true
-  - label: Create Checklist
-    agent: relentless.checklist
-    prompt: Create a checklist for the following domain...
----
-
-## User Input
-
-```text
-$ARGUMENTS
-```
-
-You **MUST** consider the user input before proceeding (if not empty).
-
-## Outline
-
-1. **Setup**: Run `.specify/scripts/bash/setup-plan.sh --json` from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\''m Groot' (or double-quote if possible: "I'm Groot").
-
-2. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`. Load IMPL_PLAN template (already copied).
-
-3. **Execute plan workflow**: Follow the structure in IMPL_PLAN template to:
-   - Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
-   - Fill Constitution Check section from constitution
-   - Evaluate gates (ERROR if violations unjustified)
-   - Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
-   - Phase 1: Generate data-model.md, contracts/, quickstart.md
-   - Phase 1: Update agent context by running the agent script
-   - Re-evaluate Constitution Check post-design
-
-4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
-
-## Phases
-
-### Phase 0: Outline & Research
-
-1. **Extract unknowns from Technical Context** above:
-   - For each NEEDS CLARIFICATION → research task
-   - For each dependency → best practices task
-   - For each integration → patterns task
-
-2. **Generate and dispatch research agents**:
-
-   ```text
-   For each unknown in Technical Context:
-     Task: "Research {unknown} for {feature context}"
-   For each technology choice:
-     Task: "Find best practices for {tech} in {domain}"
-   ```
-
-3. **Consolidate findings** in `research.md` using format:
-   - Decision: [what was chosen]
-   - Rationale: [why chosen]
-   - Alternatives considered: [what else evaluated]
-
-**Output**: research.md with all NEEDS CLARIFICATION resolved
-
-### Phase 1: Design & Contracts
-
-**Prerequisites:** `research.md` complete
-
-1. **Extract entities from feature spec** → `data-model.md`:
-   - Entity name, fields, relationships
-   - Validation rules from requirements
-   - State transitions if applicable
-
-2. **Generate API contracts** from functional requirements:
-   - For each user action → endpoint
-   - Use standard REST/GraphQL patterns
-   - Output OpenAPI/GraphQL schema to `/contracts/`
-
-3. **Agent context update**:
-   - Run `.specify/scripts/bash/update-agent-context.sh claude`
-   - These scripts detect which AI agent is in use
-   - Update the appropriate agent-specific context file
-   - Add only new technology from current plan
-   - Preserve manual additions between markers
-
-**Output**: data-model.md, /contracts/*, quickstart.md, agent-specific file
-
-## Key rules
-
-- Use absolute paths
-- ERROR on gate failures or unresolved clarifications

package/.claude/settings.local.json

@@ -1,23 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "WebSearch",
-      "Bash(amp --help:*)",
-      "Bash(opencode --help:*)",
-      "Bash(codex:*)",
-      "Bash(droid:*)",
-      "Bash(gemini:*)",
-      "Bash(node --version:*)",
-      "Bash(bun --version)",
-      "Bash(opencode agent:*)",
-      "Bash(tree:*)",
-      "Bash(jq:*)",
-      "Bash(bun run lint:*)",
-      "Bash(bun run typecheck:*)",
-      "Bash(bun build:*)",
-      "Bash(bun run:*)",
-      "Bash(git diff:*)",
-      "Bash(git add:*)"
-    ]
-  }
-}

package/.claude/skills/analyze/SKILL.md

@@ -1,149 +0,0 @@
----
-name: analyze
-description: "Analyze consistency across spec, plan, tasks, and checklist. Use before implementation. Triggers on: analyze consistency, check artifacts, validate feature."
----
-
-# Cross-Artifact Consistency Analyzer
-
-Validate consistency across feature artifacts before implementation.
-
----
-
-## The Job
-
-1. Read all feature artifacts
-2. Check for consistency issues
-3. Validate against constitution
-4. Report findings
-
----
-
-## Files to Analyze
-
-Required:
-- `relentless/constitution.md`
-- `relentless/features/NNN-feature/spec.md`
-- `relentless/features/NNN-feature/plan.md`
-- `relentless/features/NNN-feature/tasks.md`
-- `relentless/features/NNN-feature/checklist.md`
-
-Optional:
-- `relentless/features/NNN-feature/prd.json`
-- `relentless/features/NNN-feature/progress.txt`
-
----
-
-## Validation Checks
-
-### 1. Completeness
-- [ ] All functional requirements from spec have tasks
-- [ ] All tasks reference spec requirements
-- [ ] Plan addresses all spec requirements
-- [ ] Checklist covers all tasks
-
-### 2. Constitution Compliance
-- [ ] Plan follows MUST rules
-- [ ] Tasks include required quality checks
-- [ ] Testing requirements met
-- [ ] Security requirements addressed
-
-### 3. Dependency Consistency
-- [ ] Task dependencies are valid (no circular refs)
-- [ ] Referenced dependencies exist
-- [ ] Dependency order makes sense
-
-### 4. Scope Consistency
-- [ ] Plan doesn't include out-of-scope items
-- [ ] Tasks match plan scope
-- [ ] No scope creep in checklist
-
-### 5. Data Model Consistency
-- [ ] Entities mentioned in spec are in plan
-- [ ] Plan data models match spec requirements
-- [ ] Tasks create required entities
-
-### 6. API Consistency
-- [ ] Endpoints in plan match spec scenarios
-- [ ] Tasks implement all planned endpoints
-- [ ] Checklist validates all endpoints
-
-### 7. Testing Coverage
-- [ ] Each task has test acceptance criteria
-- [ ] Checklist includes test validation
-- [ ] Test types match constitution requirements
-
----
-
-## Issue Severity
-
-**CRITICAL:** Blocks implementation
-- Constitution MUST rule violations
-- Circular dependencies
-- Missing required artifacts
-
-**WARNING:** Should fix before implementation
-- Incomplete coverage of requirements
-- Ambiguous acceptance criteria
-- Missing test criteria
-
-**INFO:** Nice to have
-- Style inconsistencies
-- Minor gaps in checklist
-- Optimization opportunities
-
----
-
-## Report Format
-
-```markdown
-# Consistency Analysis: Feature Name
-
-**Date:** 2026-01-11
-**Status:** PASS / ISSUES FOUND
-
-## Summary
-- Stories: N/M completed
-- Issues: X total (Y critical, Z warnings, W info)
-
-## Critical Issues
-
-### CRIT-001: Circular Dependency
-**Location:** tasks.md
-**Details:** US-002 depends on US-003, US-003 depends on US-002
-**Fix:** Remove circular dependency, reorder tasks
-
-## Warnings
-
-### WARN-001: Missing Test Coverage
-**Location:** tasks.md, US-004
-**Details:** No integration test in acceptance criteria
-**Fix:** Add integration test requirement
-
-## Info
-
-### INFO-001: Checklist Gap
-**Location:** checklist.md
-**Details:** No performance validation for US-005
-**Suggestion:** Add performance checklist item
-
-## Recommendations
-
-1. Fix all CRITICAL issues before proceeding
-2. Address WARNINGS for better quality
-3. Consider INFO items for completeness
-
-**Next Steps:**
-- If CRITICAL issues: Fix and re-run analysis
-- If only WARNINGS: Proceed with caution
-- If PASS: Ready for `/relentless.implement`
-```
-
----
-
-## Notes
-
-- Run before starting implementation
-- Constitution compliance is non-negotiable
-- Fix critical issues immediately
-- Warnings can sometimes be deferred
-- Re-run after making fixes

package/.claude/skills/checklist/SKILL.md

@@ -1,173 +0,0 @@
----
-name: checklist
-description: "Generate quality validation checklist from spec, plan, and tasks. Use after creating tasks. Triggers on: create checklist, quality checklist, validation checklist."
----
-
-# Quality Validation Checklist Generator
-
-Generate domain-specific quality checklists to validate implementation completeness.
-
----
-
-## The Job
-
-1. Read spec.md, plan.md, and tasks.md
-2. Extract quality requirements from constitution
-3. Generate comprehensive checklist
-4. Save to `checklist.md`
-
-**Important:** Checklist items get merged into prd.json acceptance criteria!
-
----
-
-## Step 1: Locate Feature Files
-
-Verify these files exist:
-- `relentless/features/NNN-feature/spec.md`
-- `relentless/features/NNN-feature/plan.md`
-- `relentless/features/NNN-feature/tasks.md`
-
----
-
-## Step 2: Load Context
-
-Read:
-1. `relentless/constitution.md` - Quality standards and requirements
-2. Feature files (spec, plan, tasks)
-3. Identify the feature domain (auth, payments, dashboard, etc.)
-
----
-
-## Step 3: Generate Checklist Categories
-
-Create 5-7 categories based on feature domain:
-
-**Common Categories:**
-- Schema & Database
-- Backend Logic
-- Frontend Components (if applicable)
-- API Integration
-- Testing & Validation
-- Security & Permissions
-- Performance & UX
-- Documentation
-
----
-
-## Step 4: Generate Checklist Items
-
-For each category, create 5-10 specific validation items:
-
-**Format:**
-```markdown
-- [ ] CHK-001 [US-001] Specific, testable requirement
-- [ ] CHK-002 [Gap] Missing specification identified
-- [ ] CHK-003 [Ambiguity] Unclear requirement needs clarification
-- [ ] CHK-004 [Edge Case] Potential edge case to handle
-```
-
-**Guidelines:**
-- 80% of items should reference specific user stories `[US-XXX]`
-- 20% should identify gaps, ambiguities, or edge cases
-- Each item must be specific and testable
-- Total: 20-40 items across all categories
-
----
-
-## Step 5: Reference Constitution
-
-Ensure checklist includes items for constitution MUST rules:
-- Type safety requirements
-- Testing coverage
-- Security standards
-- Performance expectations
-- Code quality standards
-
----
-
-## Step 6: Save & Report
-
-1. Save to `relentless/features/NNN-feature/checklist.md`
-2. Report:
-   - Total checklist items: N
-   - Items per category
-   - Constitution compliance items: N
-   - Gaps identified: N
-   - Next step: `relentless convert tasks.md`
-
----
-
-## Example Checklist
-
-```markdown
-# Quality Checklist: User Authentication
-
-**Purpose:** Validate completeness of user authentication implementation
-**Created:** 2026-01-11
-**Feature:** [spec.md](./spec.md)
-
-## Schema & Database
-
-- [ ] CHK-001 [US-001] User table has all required fields (id, email, password_hash, confirmed, timestamps)
-- [ ] CHK-002 [US-001] Email field has UNIQUE constraint
-- [ ] CHK-003 [US-001] Indexes created on frequently queried fields (email)
-- [ ] CHK-004 [Gap] Consider adding last_login_at timestamp for analytics
-- [ ] CHK-005 [US-001] Migration script tested on clean database
-
-## Backend Logic
-
-- [ ] CHK-006 [US-001] Password hashing uses bcrypt with appropriate cost factor
-- [ ] CHK-007 [US-001] Email validation prevents common typos and invalid formats
-- [ ] CHK-008 [US-002] JWT tokens include user ID and expiration
-- [ ] CHK-009 [US-002] Token verification handles expired tokens gracefully
-- [ ] CHK-010 [Ambiguity] Password reset flow not specified - out of scope?
-
-## API Integration
-
-- [ ] CHK-011 [US-001] POST /api/auth/register returns 201 on success
-- [ ] CHK-012 [US-001] Register endpoint returns 400 for invalid email
-- [ ] CHK-013 [US-001] Register endpoint returns 409 for duplicate email
-- [ ] CHK-014 [US-002] POST /api/auth/login returns 401 for wrong password
-- [ ] CHK-015 [US-002] Login endpoint returns 403 for unconfirmed account
-- [ ] CHK-016 [Edge Case] Rate limiting on auth endpoints to prevent brute force
-
-## Testing & Validation
-
-- [ ] CHK-017 [US-001] Unit tests for password hashing utility
-- [ ] CHK-018 [US-001] Unit tests for email validation
-- [ ] CHK-019 [US-002] Integration test for full registration flow
-- [ ] CHK-020 [US-002] Integration test for login flow
-- [ ] CHK-021 [US-003] E2E test for email confirmation
-- [ ] CHK-022 [Constitution] Test coverage meets minimum 80% requirement
-
-## Security & Permissions
-
-- [ ] CHK-023 [US-001] Passwords never logged or exposed in errors
-- [ ] CHK-024 [US-001] Password requirements enforced (min length, complexity)
-- [ ] CHK-025 [US-002] JWT secret stored in environment variable, not code
-- [ ] CHK-026 [US-002] Token expiration validated on every request
-- [ ] CHK-027 [Gap] Consider adding account lockout after N failed attempts
-
-## Performance & UX
-
-- [ ] CHK-028 [US-001] Registration completes within 2 seconds
-- [ ] CHK-029 [US-002] Login completes within 1 second
-- [ ] CHK-030 [US-003] Confirmation email sent within 30 seconds
-- [ ] CHK-031 [Edge Case] Graceful handling when email service is down
-
-## Documentation
-
-- [ ] CHK-032 API endpoints documented with examples
-- [ ] CHK-033 Environment variables documented in README
-- [ ] CHK-034 Database schema documented
-```
-
----
-
-## Notes
-
-- Checklist items will be merged into acceptance criteria during convert
-- Reference user stories with `[US-XXX]` tags
-- Identify gaps and ambiguities with `[Gap]` and `[Ambiguity]` tags
-- Each item must be independently verifiable
-- Balance between comprehensiveness and practicality

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

@@ -1,40 +0,0 @@
-# [CHECKLIST TYPE] Checklist: [FEATURE NAME]
-
-**Purpose**: [Brief description of what this checklist covers]
-**Created**: [DATE]
-**Feature**: [Link to spec.md or relevant documentation]
-
-**Note**: This checklist is generated by the `/relentless.checklist` command based on feature context and requirements.
-
-<!-- 
-  ============================================================================
-  IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
-  
-  The /relentless.checklist command MUST replace these with actual items based on:
-  - User's specific checklist request
-  - Feature requirements from spec.md
-  - Technical context from plan.md
-  - Implementation details from tasks.md
-  
-  DO NOT keep these sample items in the generated checklist file.
-  ============================================================================
--->
-
-## [Category 1]
-
-- [ ] CHK001 First checklist item with clear action
-- [ ] CHK002 Second checklist item
-- [ ] CHK003 Third checklist item
-
-## [Category 2]
-
-- [ ] CHK004 Another category item
-- [ ] CHK005 Item with specific criteria
-- [ ] CHK006 Final item in this category
-
-## Notes
-
-- Check items off as completed: `[x]`
-- Add comments or findings inline
-- Link to relevant resources or documentation
-- Items are numbered sequentially for easy reference