Create implementation plans with phase management.
Creates detailed implementation plans with phases and stores them in the session folder.
/plugin marketplace add Yuvasee/samocode/plugin install yuvasee-samocode@Yuvasee/samocodeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Creates detailed implementation plans with phases, stored within the session folder.
Session path: [SESSION_PATH from working memory] Context: $ARGUMENTS
Get current time:
date '+%m-%d-%H:%M' for filename timestampdate '+%H:%M' for flow log entriesGather context:
Create plan file:
[SESSION_PATH]/[MM-DD-HH:mm]-plan-[plan-slug].mdStructure:
# Plan: [Title]
Created: [timestamp]
## Task Definition
[Concise summary]
## Requirements
- [ ] [Requirement 1]
- [ ] [Requirement 2]
## Context
[Key files, current state, constraints]
## Implementation Phases
### Phase 1: [Name]
- [ ] [Step]
- [ ] [Step]
- [ ] Run pyright/ruff or tsc - fix errors
### Phase 2: [Name]
- [ ] [Step]
- [ ] [Step]
- [ ] Run pyright/ruff or tsc - fix errors
### Phase 3: Testing
- [ ] [Test case]
- [ ] Final checks
## Notes
[Important context from task definition]
Update session:
[SESSION_PATH]/_overview.md:
- [TIMESTAMP_LOG] Plan created -> [filename].md- [filename].md - [brief description]- [filename].md - Plan: [brief description]cd [SESSION_DIR] && git add . && git commit -m "Plan: [title]"Report back: Plan summary and file location
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.