joris887
joris887/exosuit
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/joris887/exosuit --skill help-me命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Execute comprehensive backlog review. Analyzes story quality, Definition of Ready compliance, dependencies, zombie stories, and generates a backlog health report.
First-run framework setup. Detects existing project stack or guides new project creation from vision/braindump.
Use when the user has a complex idea that needs design exploration before story decomposition.
基于 SOC 职业分类
正在显示 SKILL.md
| name | help-me |
| version | 1.0.0 |
| description | Natural language skill discovery — describe what you want to do and get matched to the right skill. |
| trigger | manual |
| depends-on | [] |
| references | [] |
| disable-model-invocation | true |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep |
| argument-hint | "I want to..." |
Finding the right skill for: $ARGUMENTS
Map the user's natural language request to the most appropriate skill(s):
| User Says | Skill | Why |
|---|---|---|
| "start working", "begin", "new sprint" | /sprint-start | Creates a clean feature branch |
| "build", "implement", "add feature", "create", "deliver" | /story-cycle <description> | Full story delivery with TDD |
| "ship", "finish sprint", "create PR", "merge" | /sprint-end | Quality gates → PR → merge |
| "resume", "pick up where I left off", "continue" | /continue | Smart session resumption |
| "done for today", "end session", "save progress" | /handoff | Structured session handoff |
| User Says | Skill | Why |
|---|---|---|
| "plan", "break down", "decompose", "stories" | /ideate <idea> | Decompose into backlog stories |
| "explore design", "compare approaches", "architect" | /brainstorm <idea> | Design exploration with alternatives |
| "research", "investigate", "compare technologies" | /research <topic> | Deep online research with citations |
| User Says | Skill | Why |
|---|---|---|
| "test plan", "prepare for testing" | /manual-test | Generate test plan from changes |
| "found a bug", "test feedback", "this doesn't work" | /testing-cycle <feedback> | Classify and process test findings |
| "run UAT", "acceptance test" | /UAT-cycle <test-case-id> | Execute formal UAT test case |
| "verify UAT logic", "sense check" |
/claude-sense-check |
| Batch UAT code verification |
| "check code quality" | /code-quality | Complexity, duplication, patterns |
| "security review", "audit security" | /security-audit | CWE checklist, secrets, injection |
| "check architecture" | /architecture-check | Module boundaries, drift |
| User Says | Skill | Why |
|---|---|---|
| "debug", "error", "broken", "fix bug" | /debug-session <error> | 5-phase structured debugging |
| "fix issue", "fix #42", "github issue" | /fix-issue <number> | GitHub issue → TDD fix → PR |
| "undo", "revert", "go back", "start over" | /undo-work | Safe rollback (3 levels) |
| User Says | Skill | Why |
|---|---|---|
| "health check", "is framework ok" | /doctor | Framework health validation |
| "weekly check", "maintenance" | /weekly-maintenance | Comprehensive weekly review |
| "retrospective", "what worked" | /retrospective | Sprint review with 4Ls |
| "backlog health", "review stories" | /backlog-review | Backlog quality analysis |
| "PR status", "check PRs" | /pr-status | Open PR status + actions |
| "upgrade framework" | /framework-upgrade | Update to newer version |
| User Says | Skill | Why |
|---|---|---|
| "commit" | /commit | Conventional commit |
| "parallel", "worktree", "multiple stories" | /parallel-work | Manage concurrent worktrees |
| "improve iteratively", "refine" | /refine-loop "<task>" | Iterative self-improvement |
| "optimize metric", "increase coverage" | /optimize "<goal>" | Metric-driven optimization |
| "create skill" | /skill-create | Generate tech-specific skills |
| "test a skill" | /skill-eval | Skill testing and comparison |
| "remove framework" | /uninstall | Clean framework removal |
| "status", "dashboard" | /dashboard | Sprint status overview |
| User Says | Skill | Why |
|---|---|---|
| "review security of file" | /review-security <file> | Quick security review |
| "explain this pattern" | /explain-pattern <pattern> | Code pattern explanation |
| "suggest tests for file" | /suggest-tests <file> | Test case suggestions |
Based on the user's input, present the top 1-3 matching skills:
### Recommended
**`/skill-name <arguments>`** — [one-line description of what it does and when to use it]
### Also Consider
- `/other-skill` — [why this might also apply]
If the user's intent is ambiguous, present options using AskUserQuestion with descriptions explaining the workflow implications of each choice.
If no skill matches, suggest:
/brainstorm for complex open-ended exploration/research for information gathering