菜单
Quick feature planning that writes implementation plans to docs/plans/. Use when the user runs /plan or asks to plan a feature, endpoint, integration, or architectural change.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to dispatch a coding task to a remote workspace — fixing bugs, implementing features, running an agentic coding run, or creating a PR automatically. Use this even if the user just says "fix the login bug on myproject" or "run this task" or "create a run" or "implement X on Y". Also use when the user asks to approve or reject a pending run.
Full development workflow orchestration — requirements analysis, architecture planning, implementation, code review, and testing using specialized sub-agents with approval gates. Use when the user wants to develop a complete feature end-to-end, or asks for the full development flow. Triggers on /dev-flow.
Use when the user wants to start an AI agent (Claude, Codex, Gemini, Aider) on a remote workspace server for a project. Use this even if they just say "launch claude on myproject", "start an agent", "open a session on the server", "connect to workspace", or "I want to work on project X remotely".
Use when the user wants to manage projects on the platform — listing configured projects, adding a new repo, updating project settings, or checking if a project is cloned on its workspace. Use this for "show my projects", "add this repo", "register a new project", "which projects do I have", "is this project ready on the workspace", or any project configuration task.
Use when the user asks about workspace servers — listing them, testing SSH connectivity, checking what agents are installed, viewing server details, or troubleshooting server issues. Use this for "show me my servers", "is the server reachable", "what agents are on server X", "test connection to workspace", or any infrastructure-level question about the remote machines.
Use when the user wants to interact with a running agent session on a workspace server — sending commands, reading output, listing active sessions, or closing them. Use this for "send this to the agent", "what's the agent doing", "check session output", "close that session", "list my sessions", or any tmux-based agent interaction.
| name | plan |
| description | Quick feature planning that writes implementation plans to docs/plans/. Use when the user runs /plan or asks to plan a feature, endpoint, integration, or architectural change. |
When the user runs /plan:
docs/plans/<feature-name>.md# <Feature Name>
## Summary
One paragraph describing the feature and its purpose.
## Files to Create/Modify
| File | Action | Purpose |
|------|--------|---------|
| backend/api/... | create/modify | ... |
| backend/services/... | create/modify | ... |
| tests/unit/... | create | ... |
| frontend/src/... | create/modify | ... |
## Implementation Phases
### Phase 1: <name>
- [ ] Task with specific file and function references
- [ ] Task ...
### Phase 2: <name>
- [ ] Task ...
## Architecture Notes
- Which Protocols to implement/use (GitProvider, RoleAdapter, etc.)
- ServiceContainer integration points
- Database model changes requiring Alembic migrations
## Testing Strategy
- Unit tests for each new module
- Integration tests for cross-module flows
- Docker commands to run: `make test-file F=tests/unit/test_<module>.py`
docker compose -f docker-compose.dev.yml exec ...