superpowers-spec 1.0.0 → 1.0.1

package/README.md

@@ -20,6 +20,51 @@ This repository is a fork/evolution focused on:
 - **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)
 
+## See it in action
+
+```text
+You: /sp:propose add-dark-mode
+AI:  Created superpowers/changes/add-dark-mode/
+     ✓ proposal.md — why we're doing this, what's changing
+     ✓ specs/       — requirements and scenarios
+     ✓ design.md    — technical approach
+     ✓ tasks.md     — implementation checklist
+     Ready for implementation!
+
+You: /sp:apply
+AI:  Implementing tasks...
+     ✓ 1.1 Add theme context provider
+     ✓ 1.2 Create toggle component
+     ✓ 2.1 Add CSS variables
+     ✓ 2.2 Wire up localStorage
+     All tasks complete!
+
+You: /sp:archive
+AI:  Archived to superpowers/changes/archive/2025-01-23-add-dark-mode/
+     Specs updated. Ready for the next feature.
+```
+
+## Quickstart
+```bash
+npm i -g superpowers-spec@latest && superpowers --version
+```
+
+Inside your target project:
+
+```bash
+superpowers init
+```
+
+### 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
+
+
 ## Core concepts
 
 Superpowers with Spec manages change artifacts under `superpowers/`:
@@ -34,13 +79,13 @@ 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
+## Local development
+
+### Requirements
 
 - Node.js >= 20.19.0
 - pnpm (recommended) or npm
 
-## Local development
-
 Install dependencies:
 
 ```bash
@@ -88,14 +133,6 @@ 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
 

package/dist/core/templates/workflows/apply-change.js

@@ -160,9 +160,9 @@ This skill supports the "actions on a change" model:
 export function getSpApplyCommandTemplate() {
     return {
         name: 'SP: Apply',
-        description: 'Implement tasks from an Superpowers change (Experimental)',
+        description: 'Implement tasks from an Superpowers change',
         category: 'Workflow',
-        tags: ['workflow', 'artifacts', 'experimental'],
+        tags: ['workflow', 'artifacts'],
         content: `Implement tasks from an Superpowers change.
 
 **Input**: Optionally specify a change name (e.g., \`/sp:apply add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

package/dist/core/templates/workflows/archive-change.js

@@ -1,8 +1,8 @@
 export function getArchiveChangeSkillTemplate() {
     return {
         name: 'superpowers-archive-change',
-        description: 'Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.',
-        instructions: `Archive a completed change in the experimental workflow.
+        description: 'Archive a completed change in the workflow. Use when the user wants to finalize and archive a change after implementation is complete.',
+        instructions: `Archive a completed change in the workflow.
 
 **Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 
@@ -113,10 +113,10 @@ All artifacts complete. All tasks complete.
 export function getSpArchiveCommandTemplate() {
     return {
         name: 'SP: Archive',
-        description: 'Archive a completed change in the experimental workflow',
+        description: 'Archive a completed change in the workflow',
         category: 'Workflow',
-        tags: ['workflow', 'archive', 'experimental'],
-        content: `Archive a completed change in the experimental workflow.
+        tags: ['workflow', 'archive'],
+        content: `Archive a completed change in the workflow.
 
 **Input**: Optionally specify a change name after \`/sp:archive\` (e.g., \`/sp:archive add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
 

package/dist/core/templates/workflows/continue-change.js

@@ -117,9 +117,9 @@ For other schemas, follow the \`instruction\` field from the CLI output.
 export function getSpContinueCommandTemplate() {
     return {
         name: 'SP: Continue',
-        description: 'Continue working on a change - create the next artifact (Experimental)',
+        description: 'Continue working on a change - create the next artifact',
         category: 'Workflow',
-        tags: ['workflow', 'artifacts', 'experimental'],
+        tags: ['workflow', 'artifacts'],
         content: `Continue working on a change by creating the next artifact.
 
 **Input**: Optionally specify a change name after \`/sp:continue\` (e.g., \`/sp:continue add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

package/dist/core/templates/workflows/explore.js

@@ -297,7 +297,7 @@ export function getSpExploreCommandTemplate() {
         name: 'SP: Explore',
         description: 'Enter explore mode - think through ideas, investigate problems, clarify requirements',
         category: 'Workflow',
-        tags: ['workflow', 'explore', 'experimental', 'thinking'],
+        tags: ['workflow', 'explore', 'thinking', 'brainstorming'],
         content: `Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
 
 **IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create Superpowers artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.

package/dist/core/templates/workflows/ff-change.js

@@ -102,7 +102,7 @@ export function getSpFfCommandTemplate() {
         name: 'SP: Fast Forward',
         description: 'Create a change and generate all artifacts needed for implementation in one go',
         category: 'Workflow',
-        tags: ['workflow', 'artifacts', 'experimental'],
+        tags: ['workflow', 'artifacts'],
         content: `Fast-forward through artifact creation - generate everything needed to start implementation.
 
 **Input**: The argument after \`/sp:ff\` is the change name (kebab-case), OR a description of what the user wants to build.

package/dist/core/templates/workflows/new-change.js

@@ -1,8 +1,8 @@
 export function getNewChangeSkillTemplate() {
     return {
         name: 'superpowers-new-change',
-        description: 'Start a new Superpowers change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.',
-        instructions: `Start a new change using the experimental artifact-driven approach.
+        description: 'Start a new Superpowers change using the artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.',
+        instructions: `Start a new change using the  artifact-driven approach.
 
 **Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
 
@@ -73,10 +73,10 @@ After completing the steps, summarize:
 export function getSpNewCommandTemplate() {
     return {
         name: 'SP: New',
-        description: 'Start a new change using the experimental artifact workflow (OPSX)',
+        description: 'Start a new change using the  artifact workflow (SP)',
         category: 'Workflow',
-        tags: ['workflow', 'artifacts', 'experimental'],
-        content: `Start a new change using the experimental artifact-driven approach.
+        tags: ['workflow', 'artifacts'],
+        content: `Start a new change using the  artifact-driven approach.
 
 **Input**: The argument after \`/sp:new\` is the change name (kebab-case), OR a description of what the user wants to build.
 

package/dist/core/templates/workflows/propose.js

@@ -118,7 +118,7 @@ export function getSpProposeCommandTemplate() {
         name: 'SP: Propose',
         description: 'Propose a new change - create it and generate all artifacts in one step',
         category: 'Workflow',
-        tags: ['workflow', 'artifacts', 'experimental'],
+        tags: ['workflow', 'artifacts'],
         content: `Propose a new change - create the change and generate all artifacts in one step.
 
 I'll create a change with artifacts:

package/dist/core/templates/workflows/sync-specs.js

@@ -139,7 +139,7 @@ export function getSpSyncCommandTemplate() {
         name: 'SP: Sync',
         description: 'Sync delta specs from a change to main specs',
         category: 'Workflow',
-        tags: ['workflow', 'specs', 'experimental'],
+        tags: ['workflow', 'specs'],
         content: `Sync delta specs from a change to main specs.
 
 This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).

package/dist/core/templates/workflows/verify-change.js

@@ -169,7 +169,7 @@ export function getSpVerifyCommandTemplate() {
         name: 'SP: Verify',
         description: 'Verify implementation matches change artifacts before archiving',
         category: 'Workflow',
-        tags: ['workflow', 'verify', 'experimental'],
+        tags: ['workflow', 'verify'],
         content: `Verify that an implementation matches the change artifacts (specs, tasks, design).
 
 **Input**: Optionally specify a change name after \`/sp:verify\` (e.g., \`/sp:verify add-auth\`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "superpowers-spec",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "AI-native system for spec-driven development and test-driven development ",
   "keywords": [
     "superpowers",