Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Activate the `story-executor` skill (L1 Story Manager).
How this command is triggered — by the user, by Claude, or both
Slash command
/cognitive-architecture:planworkflow/The summary Claude sees in its command listing — used to decide when to auto-load this command
Activate the `story-executor` skill (L1 Story Manager). Arguments: $ARGUMENTS You are the L1 Story Executor. Given the Epic or backlog reference above: 1. Write a TodoWrite checklist as your first action. 2. Load `kanban_board.md` and identify the target Epic or highest-priority Todo story. 3. If given an Epic: decompose it into implementable L3 Stories with acceptance criteria, add them to the board under `## Todo`. 4. If given a specific Story: parse its type (Implementation / Test / Bug Fix), then delegate to the correct command: - Implementation → `/workflow:execute` - Te...
Activate the story-executor skill (L1 Story Manager).
Arguments: $ARGUMENTS
You are the L1 Story Executor. Given the Epic or backlog reference above:
kanban_board.md and identify the target Epic or highest-priority Todo story.## Todo./workflow:execute/workflow:test/workflow:reworkIn Progress after delegation.You never write application code. You bridge business requirements and L3 workers.
For the full operational specification, load: skills/story-executor/SKILL.md
npx claudepluginhub netzkontrast/agent-skills-for-context-engineering/planCreates a step-by-step implementation plan from requirements or a PRD file, identifying risks and dependencies, then waits for confirmation before any code changes.
/planBreaks work into small verifiable tasks with acceptance criteria and dependency ordering, saving the plan and task list to files for human review.
/planCreates three planning files (task_plan.md, findings.md, progress.md) for complex tasks and guides the user through a structured planning workflow.
/planStarts an interactive setup wizard that builds the Goal, Scope, Metric, and Verify command for an autoresearch run.
/planCreates a step-by-step implementation plan by restating requirements, identifying risks, and breaking work into phases. Waits for user confirmation before any code changes.
/planCreates strategic execution plans by capturing user intent, analyzing requirements, and generating a weighted execution strategy saved to .claude/session-plan.md.