ワンクリックでManusで任意のスキルを実行

session-start

スター3

フォーク0

更新日2026年4月13日 20:29

Bootstrap a Claude Code session by reading the feature workplan, latest journal entry, and open issues. Reports context to the user so they can confirm the session goal.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

audiocontrol-org

audiocontrol-org/audiocontrol

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Session Start

Read the following and report a concise summary to the user:

Identify the feature from the worktree name and branch:
- Run: basename $(pwd) and git rev-parse --abbrev-ref HEAD
- Extract the feature slug
Read the feature workplan:
- Read: docs/1.0/001-IN-PROGRESS/<feature-slug>/README.md
- Read: docs/1.0/001-IN-PROGRESS/<feature-slug>/workplan.md
- Note: current phase, completed tasks, next tasks
Read the latest DEVELOPMENT-NOTES.md entry:
- Read: DEVELOPMENT-NOTES.md (last entry only)
- Note: what was accomplished, what failed, course corrections
Read device notes if applicable:
- If the feature involves SCSI/device work: read SCSI-NOTES.md (last 2-3 entries)
Read the session analysis report (if it exists):
- Read: data/sessions/report-all.md — look for the "LLM Session Analysis" section
- Note: top correction categories, most common patterns, improvement suggestions
- These are mistakes from previous sessions — actively avoid repeating them
Check open GitHub issues:
- Run: gh issue list --label <relevant-label> --state open
Check testing infrastructure (if the feature involves UI work):
- Read: TESTING.md for the overall test architecture (unit/ui/e2e categories)
- Read: TESTING-UI.md for the UI test methodology
- Check if a test harness page exists: src/pages/Test<Feature>Page.tsx
- Check if UI test specs exist: test/ui/<feature>.spec.ts
- If harness missing: flag that it should be created before implementation
- If specs missing: flag that every manually verified interaction needs a spec
Report to the user:
- Feature name and current phase
- Last session's key accomplishments and failures
- Top correction patterns to watch for (from analysis report)
- Top unresolved issues
- Proposed goal for this session

Do NOT start coding until the user confirms the session goal.

このリポジトリの他の Skills

同じリポジトリ

scope-inventory

audiocontrol-org/audiocontrol

Run upfront discovery for a system-wide feature. Fans out discovery agents in parallel, synthesizes a strawman scope-manifest.yaml, writes the evidence trail to the feature docs directory.

2026-05-223

scope-widen

audiocontrol-org/audiocontrol

Run targeted discovery for a mid-implementation operator complaint. Identifies all sibling surfaces consuming the same primitive/pattern; produces a widening proposal in the dispatch-wrapper-grammar format.

2026-05-223

release-midi-macro-bridge

audiocontrol-org/audiocontrol

Use when shipping a new midi-macro-bridge version — bumping Cargo.toml, cutting a v-tag, publishing a GitHub Release, or updating the Homebrew tap.

2026-05-063

feature-extend

audiocontrol-org/audiocontrol

Extend a feature's scope mid-implementation by adding new phases to the existing docs and issue plan without creating a new branch or worktree.

2026-04-173

feature-help

audiocontrol-org/audiocontrol

Explain the audiocontrol feature lifecycle and report the current state of active, in-progress, or partially defined features.

2026-04-173

session-end

audiocontrol-org/audiocontrol

Wrap up a Codex work session by updating feature docs, recording development notes, and closing the loop on issue and hardware notes where needed.

2026-04-173

Session Start

Read the following and report a concise summary to the user:

Identify the feature from the worktree name and branch:

Run: basename $(pwd) and git rev-parse --abbrev-ref HEAD
Extract the feature slug

Read the feature workplan:

Read: docs/1.0/001-IN-PROGRESS/<feature-slug>/README.md
Read: docs/1.0/001-IN-PROGRESS/<feature-slug>/workplan.md
Note: current phase, completed tasks, next tasks

Read the latest DEVELOPMENT-NOTES.md entry:

Read: DEVELOPMENT-NOTES.md (last entry only)
Note: what was accomplished, what failed, course corrections

Read device notes if applicable:

If the feature involves SCSI/device work: read SCSI-NOTES.md (last 2-3 entries)

Read the session analysis report (if it exists):

Read: data/sessions/report-all.md — look for the "LLM Session Analysis" section
Note: top correction categories, most common patterns, improvement suggestions
These are mistakes from previous sessions — actively avoid repeating them

Check open GitHub issues:

Run: gh issue list --label <relevant-label> --state open

Check testing infrastructure (if the feature involves UI work):

Read: TESTING.md for the overall test architecture (unit/ui/e2e categories)
Read: TESTING-UI.md for the UI test methodology
Check if a test harness page exists: src/pages/Test<Feature>Page.tsx
Check if UI test specs exist: test/ui/<feature>.spec.ts
If harness missing: flag that it should be created before implementation
If specs missing: flag that every manually verified interaction needs a spec

Report to the user:

Feature name and current phase
Last session's key accomplishments and failures
Top correction patterns to watch for (from analysis report)
Top unresolved issues
Proposed goal for this session

Do NOT start coding until the user confirms the session goal.

name	session-start
description	Bootstrap a Claude Code session by reading the feature workplan, latest journal entry, and open issues. Reports context to the user so they can confirm the session goal.
user_invocable	true