peaks-cli 1.0.0

package/skills/peaks-solo/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: peaks-solo
+description: Full-auto orchestration facade for the Peaks skill family. Use when the user asks Peaks to handle a project workflow end-to-end, especially refactoring via `peaks-solo refactor`, coordinating peaks-prd, peaks-rd, peaks-qa, peaks-sc, and peaks-txt while preserving user confirmation gates.
+---
+
+# Peaks Solo
+
+Peaks Solo is the orchestration facade for the Peaks short skill family.
+
+Use this skill to identify the user scenario, recommend an execution mode, coordinate role skills, and produce the final handoff report. Do not collapse role responsibilities into this skill.
+
+## Boundaries
+
+Peaks Solo may:
+
+- identify scenarios such as refactor, bugfix, QA hardening, release validation, and incident response;
+- recommend Solo, Assisted, Swarm, or Strict profiles;
+- coordinate Peaks role skills through artifacts;
+- coordinate project memory extraction from stable skill artifact sections;
+- request user confirmation at risk and commit boundaries;
+- read CLI doctor/profile/artifact reports.
+
+Peaks Solo must not silently:
+
+- install hooks;
+- create agents;
+- enable MCP servers;
+- modify Claude settings;
+- create GitHub repositories;
+- bypass role-skill artifacts.
+
+Use the Peaks CLI for runtime side effects.
+
+## Project standards preflight
+
+Before orchestrating an end-to-end code repository workflow, gather the project standards preflight status from RD and QA by calling the Peaks CLI:
+
+- `peaks standards init --project <path> --dry-run`
+- `peaks standards update --project <path> --dry-run`
+
+Use `standards init` for first-time creation and `standards update` for existing `CLAUDE.md` append/review behavior. Apply only when write authorization exists; otherwise keep the CLI output as the next action and continue only when the selected workflow can safely proceed without writing standards. Do not hand-write standards file mutations inside the skill.
+
+## Refactor mode
+
+Read `references/refactor-mode.md` before handling refactor requests.
+
+Default MVP path: `peaks-solo refactor`.
+
+It must enforce the shared refactor red lines:
+
+1. understand the project before changes;
+2. require UT coverage >= 95%;
+3. treat unknown coverage as failing;
+4. split broad refactors into minimal functional slices;
+5. require strict verifiable specs before each slice;
+6. require 100% acceptance for each slice;
+7. require code and intermediate artifacts to be committed before the next slice.
+
+## Optional capabilities
+
+When built-in guidance is insufficient, use capability discovery rather than reimplementing specialist workflows. Ask for user consent before token-heavy discovery unless the active profile permits it.
+
+Reference: `references/workflow.md`.

package/skills/peaks-solo/references/artifact-contracts.md

@@ -0,0 +1,3 @@
+# artifact-contracts.md
+
+This reference documents artifact-contracts.md for peaks-solo.

package/skills/peaks-solo/references/command-migration.md

@@ -0,0 +1,3 @@
+# command-migration.md
+
+This reference documents command-migration.md for peaks-solo.

package/skills/peaks-solo/references/refactor-mode.md

@@ -0,0 +1,22 @@
+# Peaks Solo Refactor Mode
+
+`peaks-solo refactor` is the primary MVP path.
+
+## Flow
+
+1. Detect refactor intent and risk.
+2. Ask CLI doctor for available runtime capabilities.
+3. Coordinate `peaks-prd` for goals, non-goals, preserved behavior, and acceptance spec.
+4. Coordinate `peaks-txt` for initial context capsule.
+5. Coordinate `peaks-rd` for project scan, standards scan, coverage report, slice map, and options.
+6. Block implementation unless UT coverage is >= 95%.
+7. Coordinate `peaks-qa` for regression matrix and baseline report.
+8. Ask the user to confirm option, scope, and accepted risks.
+9. Execute one minimal functional slice at a time.
+10. Require 100% acceptance for the slice.
+11. Coordinate `peaks-sc` for artifact retention and commit boundary.
+12. Refuse the next slice until code and intermediate artifacts are committed.
+
+## Runtime resources
+
+Use CLI-managed profiles for hooks, agents, swarm, MCP, and external skills. Do not install them from the skill body.

package/skills/peaks-solo/references/workflow.md

@@ -0,0 +1,14 @@
+# Peaks Solo Workflow
+
+Peaks Solo is a facade over role skills. It keeps the workflow moving without absorbing role-specific responsibility.
+
+## Modes
+
+- Solo: default, single controller with soft gates.
+- Assisted: role skills contribute artifacts without broad swarm execution.
+- Swarm: multiple subagents work in parallel when the CLI-managed profile is enabled.
+- Strict: hook/profile guarded mode for high-risk work.
+
+## Capability discovery
+
+Before using `find-skills`, explain the benefit and token cost unless the active profile permits automatic discovery.

package/skills/peaks-txt/SKILL.md

@@ -0,0 +1,48 @@
+---
+name: peaks-txt
+description: Context and knowledge skill for Peaks. Use when a workflow needs context capsules, role-specific context slices, decision records, assumptions, discarded options, staleness checks, lessons, or reusable project memory.
+---
+
+# Peaks TXT
+
+Peaks TXT compresses workflow context into portable, role-specific artifacts.
+
+## Responsibilities
+
+- generate context capsules;
+- slice context for PRD, RD, QA, UI, and SC consumers;
+- record decisions, assumptions, discarded options, and staleness conditions;
+- archive lessons from refactor slices.
+
+## Refactor role
+
+For refactors, create initial context before RD analysis and final context after validation and artifact retention.
+
+## Project memory guidance
+
+When a skill artifact contains reusable project facts, decisions, rules, or constraints, mark only the stable extract with:
+
+```markdown
+<!-- peaks-memory:start -->
+title: Short project memory title
+kind: project
+---
+Stable memory body.
+<!-- peaks-memory:end -->
+```
+
+The primary write target is the target project's `.claude/memory`. Use `peaks memory extract --project <path> --artifact <artifact> --apply` only after the user or active profile allows durable project memory writes.
+
+## External capability guidance
+
+Use `peaks capabilities --json` before recommending memory or context-management resources.
+
+- claude-mem and context-mode can inform reusable context workflows only when durable memory is explicitly approved.
+- Never store secrets, credentials, private customer data, or non-exportable business data in memory artifacts.
+- Prefer Peaks TXT context capsules when external persistence is unavailable or not authorized.
+
+## Boundaries
+
+Do not choose the refactor plan or install runtime resources. Use artifacts produced by other skills and CLI reports.
+
+Reference: `references/context-capsule.md`.

package/skills/peaks-txt/references/artifact-contracts.md

@@ -0,0 +1,3 @@
+# artifact-contracts.md
+
+This reference documents artifact-contracts.md for peaks-txt.

package/skills/peaks-txt/references/command-migration.md

@@ -0,0 +1,3 @@
+# command-migration.md
+
+This reference documents command-migration.md for peaks-txt.

package/skills/peaks-txt/references/context-capsule.md

@@ -0,0 +1,20 @@
+# Context Capsule
+
+A context capsule is the smallest durable context needed by downstream roles.
+
+## Contents
+
+- original request;
+- goals and non-goals;
+- confirmed decisions;
+- assumptions;
+- discarded options;
+- risks;
+- role-specific slices;
+- staleness conditions.
+
+Do not dump full conversations into downstream artifacts.
+
+## Durable project memory
+
+Only stable and reusable project facts should be marked for memory extraction. Use `.claude/memory` as the project-local primary source, and let Peaks SC sync that directory to the artifact repository at checkpoints.

package/skills/peaks-ui/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: peaks-ui
+description: UI and experience skill for Peaks. Use when a workflow touches UI/UX, interaction design, visual direction, design systems, frontend page behavior, high-fidelity HTML prototypes, or UI regression seeds.
+---
+
+# Peaks UI
+
+Peaks UI handles experience, interaction, visual direction, and UI-specific refactor artifacts.
+
+## Responsibilities
+
+- identify when UI involvement is necessary;
+- produce UX flow and page-state artifacts;
+- define interaction and visual constraints;
+- create UI regression seeds;
+- review user-facing behavior preservation.
+
+## Refactor role
+
+Only engage when the refactor affects UI, interaction, styling, page structure, design system, or frontend user behavior.
+
+## External capability guidance
+
+Use `peaks capabilities --json` before recommending design, browser, or UI reference resources.
+
+- shadcn/ui, React Bits, awesome-design-md, taste-skill, and ui-ux-pro-max-skill are UI references; do not treat unreviewed generated UI as finished design.
+- Chrome DevTools MCP and Agent Browser can support runtime UI inspection only after the user approves the app target.
+- Figma Context MCP and Penpot require user-authorized design access and must not persist tokens or private design data in project artifacts.
+- Check license, accessibility, and performance before translating external visual references into Peaks UI constraints.
+
+## Boundaries
+
+Do not own backend architecture, non-UI implementation, runtime hook installation, or final QA acceptance.
+
+Reference: `references/workflow.md`.

package/skills/peaks-ui/references/artifact-contracts.md

@@ -0,0 +1,3 @@
+# artifact-contracts.md
+
+This reference documents artifact-contracts.md for peaks-ui.

package/skills/peaks-ui/references/command-migration.md

@@ -0,0 +1,3 @@
+# command-migration.md
+
+This reference documents command-migration.md for peaks-ui.

package/skills/peaks-ui/references/workflow.md

@@ -0,0 +1,11 @@
+# Peaks UI Workflow
+
+Use Peaks UI only when refactor scope affects user-facing behavior, interaction, visual structure, design systems, or page states.
+
+## Outputs
+
+- UX flow;
+- page state map;
+- interaction constraints;
+- UI regression seeds;
+- accessibility notes.