peaks-cli 1.0.14 → 1.0.15

package/skills/peaks-qa/SKILL.md

@@ -7,6 +7,16 @@ description: QA and verification skill for Peaks. Use when a workflow needs unit
 
 Peaks QA proves that planned changes are protected and accepted.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-qa --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-qa | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-qa --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - inspect unit-test coverage evidence;

package/skills/peaks-rd/SKILL.md

@@ -7,6 +7,16 @@ description: Research and development skill for Peaks. Use for engineering analy
 
 Peaks RD owns engineering analysis, implementation planning, and refactor execution contracts.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-rd --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-rd | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-rd --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - scan the current project before changes;

package/skills/peaks-sc/SKILL.md

@@ -7,6 +7,16 @@ description: Source control, sync, and change-control skill for Peaks. Use when
 
 Peaks SC records how product, RD, QA, code, and artifacts move together.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-sc --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-sc | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-sc --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - produce change-impact artifacts;

package/skills/peaks-solo/SKILL.md

@@ -9,6 +9,18 @@ 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.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis, response, or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-solo --mode <mode> --gate startup
+```
+
+Then display the compact status header: `Peaks Skill: peaks-solo | Gate: startup | Next: <one short action>`. Display this header on EVERY turn while the skill is active.
+
+Update with `peaks skill presence:set peaks-solo --mode <mode> --gate <gate>` when gates change. When the workflow ends, run `peaks skill presence:clear`.
+
 ## Boundaries
 
 Peaks Solo may:

package/skills/peaks-txt/SKILL.md

@@ -7,6 +7,16 @@ description: Context and knowledge skill for Peaks. Use when a workflow needs co
 
 Peaks TXT compresses workflow context into portable, role-specific artifacts.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-txt --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-txt | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-txt --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - generate context capsules;
@@ -19,6 +29,16 @@ Peaks TXT compresses workflow context into portable, role-specific artifacts.
 
 For refactors, create initial context before RD analysis and final context after validation and artifact retention.
 
+## Artifact boundary vs PRD / UI / RD / QA / SC
+
+Peaks TXT is intentionally not a `peaks request <role>` role. The other five roles each own a per-request artifact at `.peaks/<session-id>/<role>/requests/<request-id>.md` with a role-specific state machine that `peaks request init/list/show/transition` validates. TXT artifacts live at one level up:
+
+- session-scoped lessons: `.peaks/<session-id>/txt/skill-usage-lessons.md`;
+- role-scoped or topic-scoped context capsules: `.peaks/<session-id>/txt/<role>-capsule.md`, `.peaks/<session-id>/txt/<topic>-capsule.md`;
+- compact handoff capsules referenced by other roles' artifacts.
+
+This boundary keeps TXT a meta layer that consumes other roles' artifacts and CLI reports, not a workflow stage. Cross-link from a TXT capsule body to the relevant request artifacts instead of duplicating their content. Do not invoke `peaks request init --role txt`; the CLI rejects it.
+
 ## Compaction-safe outputs
 
 When used alone or when a workflow needs portable artifacts that must survive session compaction, end with a short structured capsule: mode, validated decisions, artifact paths, standards deltas, open questions, and next action. Prefer links or paths over long narrative. Do not duplicate the full workflow log when a compact capsule is enough.

package/skills/peaks-ui/SKILL.md

@@ -7,6 +7,16 @@ description: UI and experience skill for Peaks. Use when a workflow touches UI/U
 
 Peaks UI handles experience, interaction, visual direction, and UI-specific refactor artifacts.
 
+## Skill presence (MANDATORY first action)
+
+Before any analysis or tool call, immediately run:
+
+```bash
+peaks skill presence:set peaks-ui --mode <mode> --gate startup
+```
+
+Then display: `Peaks Skill: peaks-ui | Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-ui --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear`.
+
 ## Responsibilities
 
 - identify when UI involvement is necessary;