メニュー
Use when you need quick code implementation for features, bug fixes, or utilities.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/seokan-jeong/team-shinchan --skill team-shinchan-implementコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when you want to start a new task with the integrated workflow.
Use when you want autonomous completion from requirements to verification without intervention.
Use when you need backend development for APIs, databases, servers, or endpoints.
SKILL.md を表示中
SOC 職業分類に基づく
| name | team-shinchan:implement |
| description | Use when you need quick code implementation for features, bug fixes, or utilities. |
| user-invocable | false |
If args is empty or only whitespace:
Ask user: "What would you like me to implement?"
STOP and wait for user response
If args length > 2000 characters:
Truncate to 2000 characters
Warn user: "Request was truncated to 2000 characters"
Read ${CLAUDE_PLUGIN_ROOT}/agents/_shared/domain-router.json to determine the target agent.
Detection logic (apply in order):
.tsx → frontend)Routing decision:
subagent_type="team-shinchan:aichan"subagent_type="team-shinchan:buriburi"subagent_type="team-shinchan:masao"subagent_type="team-shinchan:bo" (fallback)Before dispatching, run the START → In Progress transition per
agents/_shared/linear-sync.md: detect a Linear issue in args/branch, confirm it
with , and if real move it to In Progress. No-op if no Linear issue / Linear
MCP unavailable — never block the work.
get_issueDo not read further. Execute this Task NOW:
Task(
subagent_type="{detected_agent from Step 2}",
model="sonnet",
prompt=`/team-shinchan:implement has been invoked.
## Implementation Request
Handle coding tasks including:
| Area | Capabilities |
|------|-------------|
| Feature Implementation | New features, functions, classes |
| Bug Fixes | Debugging, error correction |
| Code Modification | Refactoring, updates, changes |
| Utilities | Helper functions, utilities |
| Tests | Unit tests, integration tests |
## Implementation Requirements
- Read existing code first to understand patterns
- Follow project conventions
- Write clean, maintainable code
- Handle errors gracefully
- Keep functions small and focused
- Add comments only for complex logic
## Post-Implementation Verification
After writing code:
1. Run existing tests if available (detect test framework from package.json/config)
2. If tests fail, fix the issues before reporting completion
3. If no tests exist, verify the code compiles/loads without errors
## Output Format
After implementation:
- Summary of changes made
- Files modified with line references
- Test results (pass/fail/skipped)
- Any follow-up recommendations
User request: ${args || '(Please describe what to implement)'}
`
)
After the Task returns successfully, run the FINISH → In Review transition per
agents/_shared/linear-sync.md for the same issue (no-op if not Linear-based), then STOP.
STOP HERE. The above Task handles everything.