メニュー
Manage your Specrew Crew Interaction Profile — how much Specrew asks, explains, recommends, and auto-decides during specification intake.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Perform a Specrew human-verdict boundary stop on the Claude host. Renders the FULL Rule 46 six-section human re-entry packet AND the verdict options as one Markdown message, with the AskUserQuestion picker disabled so the packet cannot collapse into the picker's short header/option fields. Invoke at EVERY human-judgment boundary stop (specify, clarify, plan, tasks, before-implement, implement, review, retro, feature-closeout, lifecycle-end). Triggers: boundary stop, verdict, approve / redirect / send back, why I stopped, human re-entry packet, gate stop.
{what this skill teaches agents}
Run Specrew's per-lens design workshop and collaborative design-analysis. Use whenever you work the design lenses for a feature: at specify/intake (the lens workshop) and at the design-analysis stop (co-design the architecture), and RE-INVOKE at the start of EACH new lens (architecture, data, ui-ux, security, integration, devops, requirements/NFR, observability, component). Triggers: design, design lens, lens workshop, design-analysis, architecture, trade-offs, co-design, explore options, decompose, or moving from one lens to the next. Tells you to facilitate each lens as a discussion, surface diagrams the human can actually SEE (console ASCII inline; mermaid/html to a file with a clickable file:/// link), co-design components/responsibilities/flows WITH the human instead of handing over finished options, capture the agreements, and which per-lens md to load.
| name | specrew-user-profile |
| description | Manage your Specrew Crew Interaction Profile — how much Specrew asks, explains, recommends, and auto-decides during specification intake. |
Type: Configuration Skill
Schema: v1
Status: Active
Namespace: /specrew
Canonical command: /specrew-user-profile
Manage your Crew Interaction Profile — four decision-area settings that tell Specrew how much to
ask, explain, recommend, and auto-decide for you. Higher settings (7–10) get concise, expert-level
questions and assume you make the call; lower or auto settings get more explanation, recommended
defaults, and transparent auto-decisions.
The four visible decision areas are Product Strategy, UX/UI Design, Software Architecture, and AI Delivery Planning. They are display labels for collaboration settings — not job titles you must hold, and not Specrew's internal persona lenses (the perspectives the intake engine applies to your request). Your profile tunes how Specrew talks to you; the persona lenses are Specrew's internal analysis machinery and are unaffected by what you choose here.
The profile resolves per current user from a local file (the loader/path rule) and is reused across all Specrew projects:
$env:USERPROFILE\.specrew\user-profile.yml~/.specrew/user-profile.ymlDisplay the current Crew Interaction Profile with readable descriptions.
Invocation:
/specrew-user-profile show
Example output:
Crew Interaction Profile (current user):
- Product Strategy: 7 (Senior — concise questions; you decide)
- UX/UI Design: auto (Specrew recommends defaults and explains)
- Software Architecture: 9 (Senior — concise questions; you decide)
- AI Delivery Planning: 2 (Learning — Specrew explains and auto-decides with transparency)
To update: use /specrew-user-profile edit or /specrew-user-profile reset
Interactively update your decision-area settings. Prompts for each decision area; press Enter to keep the current value.
Invocation:
/specrew-user-profile edit
Interactive flow:
Delete the profile file, triggering first-run setup on the next specrew start.
Invocation:
/specrew-user-profile reset
Warning: This is destructive. The existing profile will be deleted and you will be prompted to
reconfigure on next specrew start.
Backed by: scripts/internal/user-profile.ps1 helper functions.
Shell invocation:
# Show profile
. C:\Dev\Specrew\scripts\internal\user-profile.ps1
$profile = Get-UserProfile
Show-UserProfileSummary -Profile $profile
# Edit profile
. C:\Dev\Specrew\scripts\internal\user-profile.ps1
Edit-UserProfile
# Reset profile
. C:\Dev\Specrew\scripts\internal\user-profile.ps1
Reset-UserProfile
For portable execution from any Specrew-managed project:
$userProfileHelper = Join-Path (Get-Module Specrew -ListAvailable | Sort-Object Version -Descending | Select-Object -First 1).ModuleBase 'scripts\internal\user-profile.ps1'
if (Test-Path $userProfileHelper) {
. $userProfileHelper
# Then call Show-UserProfileSummary, Edit-UserProfile, or Reset-UserProfile
}
| Range | Setting | How Specrew collaborates |
|---|---|---|
| 7-10 | Senior | Concise, expert-level questions; assumes you make the call; minimal auto-decisions |
| 4-6 | Standard | Targeted clarifications |
| 1-3 | Learning | Specrew explains more and auto-decides with transparency annotations |
| auto | "you decide for me" | Specrew recommends defaults and explains them |
/speckit.specify: that surface uses your settings to drive per-lens
question depth and auto-decisions. No other surface hard-applies the profile in this release.Display labels are display metadata only. The persisted schema keys (expertise.*, including
ai_research_project_management) and Specrew's internal persona IDs (including
ai-researcher-project-manager) are stable internal contracts and are never renamed or migrated.
Profiles created before this wording correction keep working unchanged — only the visible labels and
explanatory text changed.
$env:USERPROFILE\.specrew\user-profile.yml~/.specrew/user-profile.ymlThe profile persists across all Specrew projects for the current user. Because it lives in your home directory and is never written into shared repository artifacts, teammates can run different local profiles in the same repository without any shared-repository changes.
/speckit.specify — the only surface that hard-applies the Crew Interaction Profile to tailor intake depthspecrew start — prompts for your Crew Interaction Profile on first run if the profile is missingThis skill modifies user-level configuration only. It does not authorize or imply approval to advance any lifecycle boundary.
Part of the /specrew-* command surface. Coexists with /speckit.* without collision.