superpowers-spec 1.0.0

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2024 OpenSpec Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

package/README.md

@@ -0,0 +1,141 @@
+# Superpowers with Spec
+
+Superpowers with Spec is an AI-native CLI for spec-driven development.
+
+It combines:
+
+- OpenSpec's structured artifact workflow and CLI foundations: proposal/design/tasks/spec lifecycle
+- Superpowers' practical skill library for brainstorming, planning, execution, debugging, and verification
+
+Project base references:
+
+- OpenSpec: https://github.com/Fission-AI/OpenSpec
+- Superpowers skills: https://github.com/obra/superpowers
+
+## What this project is
+
+This repository is a fork/evolution focused on:
+
+- **OpenSpec-style rigor**: explicit artifacts, traceable changes, predictable implementation flow
+- **Superpowers-style productivity**: reusable skills that guide agent behavior in real coding sessions
+- **Tool-agnostic setup**: generated skills/commands for many coding agents (including Codex)
+
+## Core concepts
+
+Superpowers with Spec manages change artifacts under `superpowers/`:
+
+- `superpowers/changes/<change>/proposal.md`
+- `superpowers/changes/<change>/design.md`
+- `superpowers/changes/<change>/tasks.md`
+- `superpowers/changes/<change>/specs/...`
+
+And installs agent-facing assets under tool directories (for example):
+
+- `.claude/skills`, `.claude/commands`, `.claude/hooks`, `.claude/agents`
+- `.codex/skills`, global Codex prompts under `~/.codex/prompts`, plus `.codex/hooks` and `.codex/agents`
+
+## Requirements
+
+- Node.js >= 20.19.0
+- pnpm (recommended) or npm
+
+## Local development
+
+Install dependencies:
+
+```bash
+pnpm install
+```
+
+Build:
+
+```bash
+pnpm run build
+```
+
+Run tests:
+
+```bash
+pnpm test
+```
+
+Lint:
+
+```bash
+pnpm run lint
+```
+
+Run CLI locally from repo:
+
+```bash
+node bin/superpowers.js --help
+node bin/superpowers.js --version
+```
+
+## Initialize in a project
+
+Inside your target project:
+
+```bash
+superpowers init
+```
+
+Or non-interactive:
+
+```bash
+superpowers init --tools codex
+superpowers init --tools claude,cursor
+superpowers init --tools all
+```
+
+## Main commands
+
+- `superpowers init` — initialize project and tool assets
+- `superpowers update` — refresh installed skills/commands from current profile
+- `superpowers list` — list changes (or specs with flags)
+- `superpowers show` — show artifacts/specs
+- `superpowers validate` — validate artifacts/specs
+- `superpowers config profile` — switch workflow profile
+
+## Repository structure
+
+- `src/` — TypeScript source
+- `skills/` — bundled static skills copied to tool directories
+- `hooks/` — bundled hook files
+- `agents/` — bundled agent definitions
+- `schemas/` — schema templates and validation schema
+- `test/` — Vitest test suite
+
+## Publish to npm
+
+Before publish:
+
+```bash
+pnpm run build
+pnpm test
+pnpm run check:pack-version
+```
+
+Publish flow:
+
+```bash
+pnpm changeset
+pnpm changeset version
+pnpm run release:ci
+```
+
+Package metadata is in `package.json` (current package name: `superpowers-spec`).
+
+## Telemetry
+
+Anonymous command telemetry is enabled by default and can be disabled via:
+
+```bash
+export SUPERPOWERS_TELEMETRY=0
+# or
+export DO_NOT_TRACK=1
+```
+
+## License
+
+MIT

package/agents/code-reviewer.md

@@ -0,0 +1,48 @@
+---
+name: code-reviewer
+description: |
+  Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>
+model: inherit
+---
+
+You are a Senior Code Reviewer with expertise in software architecture, design patterns, and best practices. Your role is to review completed project steps against original plans and ensure code quality standards are met.
+
+When reviewing completed work, you will:
+
+1. **Plan Alignment Analysis**:
+   - Compare the implementation against the original planning document or step description
+   - Identify any deviations from the planned approach, architecture, or requirements
+   - Assess whether deviations are justified improvements or problematic departures
+   - Verify that all planned functionality has been implemented
+
+2. **Code Quality Assessment**:
+   - Review code for adherence to established patterns and conventions
+   - Check for proper error handling, type safety, and defensive programming
+   - Evaluate code organization, naming conventions, and maintainability
+   - Assess test coverage and quality of test implementations
+   - Look for potential security vulnerabilities or performance issues
+
+3. **Architecture and Design Review**:
+   - Ensure the implementation follows SOLID principles and established architectural patterns
+   - Check for proper separation of concerns and loose coupling
+   - Verify that the code integrates well with existing systems
+   - Assess scalability and extensibility considerations
+
+4. **Documentation and Standards**:
+   - Verify that code includes appropriate comments and documentation
+   - Check that file headers, function documentation, and inline comments are present and accurate
+   - Ensure adherence to project-specific coding standards and conventions
+
+5. **Issue Identification and Recommendations**:
+   - Clearly categorize issues as: Critical (must fix), Important (should fix), or Suggestions (nice to have)
+   - For each issue, provide specific examples and actionable recommendations
+   - When you identify plan deviations, explain whether they're problematic or beneficial
+   - Suggest specific improvements with code examples when helpful
+
+6. **Communication Protocol**:
+   - If you find significant deviations from the plan, ask the coding agent to review and confirm the changes
+   - If you identify issues with the original plan itself, recommend plan updates
+   - For implementation problems, provide clear guidance on fixes needed
+   - Always acknowledge what was done well before highlighting issues
+
+Your output should be structured, actionable, and focused on helping maintain high code quality while ensuring project goals are met. Be thorough but concise, and always provide constructive feedback that helps improve both the current implementation and future development practices.

package/bin/openspec.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+import '../dist/cli/index.js';

package/bin/superpowers.js

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+
+import '../dist/cli/index.js';

package/dist/cli/index.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=index.d.ts.map