用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/asermax/claude-plugins --skill retrofit-spec命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | retrofit-spec |
| description | Create a feature specification from existing code |
| argument-hint | <path> |
| disable-model-invocation | true |
Create a feature specification from existing code implementation.
Path to file or module: $ARGUMENTS
You must load the following skills and read the following files before proceeding.
katachi:retrofit-existing - Retrofit workflowdocs/feature-specs/ - Existing feature documentation to understand organizationdocs/feature-specs/README.md - Top-level feature index (if exists)docs/planning/VISION.md - Project context for inferenceVerify:
Read the target file(s):
Task(
subagent_type="katachi:codebase-analyzer",
prompt=f"""
Analyze this code to create a feature specification.
## Analysis Type
spec
## Target Files
{file_contents}
## Project Context
{vision_content if exists else "No VISION.md - infer project context from code"}
"""
)
Show the agent's draft spec:
## Draft Specification
Based on analyzing [path], here's a draft spec:
[Draft spec content]
---
### Notes from Analysis
- [Assumptions made]
- [Uncertainties]
- [Areas needing clarification]
What needs adjustment in this spec?
User provides corrections:
Continue iteration until user approves.
Analyze existing feature-specs/ structure:
"Looking at existing feature documentation, where should this belong?
Existing capability domains:
- auth/ - [description]
- api/ - [description]
- [etc.]
Should this be:
A) New sub-capability in existing domain (e.g., auth/new-feature.md)
B) New capability domain (create new folder)
C) Standalone feature (top-level .md file)
Which organization makes sense?"
Write spec to appropriate location in docs/feature-specs/:
docs/feature-specs/[domain]/[feature].mddocs/feature-specs/[feature].mdInclude retrofit note:
# [Feature Name]
## Retrofit Note
This spec was created from existing code at `[path]`.
Original implementation date: [Unknown / from git history if available]
---
[Rest of spec content]
## Related Deltas
(To be added when deltas implement changes to this feature)
If adding to existing domain:
docs/feature-specs/[domain]/README.mdIf creating new domain:
docs/feature-specs/[domain]/README.mddocs/feature-specs/README.md"Feature spec created for existing code:
File: docs/feature-specs/[path]
Type: [Domain/Sub-capability/Standalone]
The feature documentation has been created. You can now:
- Retrofit design rationale: /katachi:retrofit-design [path]
- Retrofit another module: /katachi:retrofit-spec <path>
- Document a specific decision: /katachi:retrofit-decision <topic>
**Recommended next step:** Run `/katachi:retrofit-design [path]` to:
- Capture the design rationale behind the implementation
- Automatically discover and document undocumented ADR/DES patterns
- Create a complete design document from the existing code"
This is a collaborative process: