task-pipeline
Structured workflow for grill notes → research → plan → tickets → work. Use when starting or continuing a task with /task, /plan, /tickets, /continue, or /retrieve commands.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Structured workflow for grill notes → research → plan → tickets → work. Use when starting or continuing a task with /task, /plan, /tickets, /continue, or /retrieve commands.
Create and refine tickets for the tk ticket system. Use when the user says 'create tickets for X', 'refine ticket X', 'break this into tickets', 'seed tickets from plan', or anything about creating or refining tk tickets.
Only to be triggered by explicit /parallel-task-tmux commands. Dependency-aware parallel plan execution that launches each unblocked Codex worker in a live tmux pane, keeps pane output visible in real time, and shrinks the layout by closing panes as tasks complete.
Use when helping with daily planning, task prioritization, reviewing agenda, or when user seems stuck on what to do next
Import existing project documentation into a block-level PlanWeave Plan Package and validate it through the PlanWeave CLI. Use when importing PRDs, roadmaps, issue sets, architecture notes, or another strong source plan.
Create a PlanWeave package-shaped plan draft from a fuzzy goal, sparse requirements, codebase context, or a user idea before a formal Plan Package exists. Use when the user asks to make, draft, design, break down, or plan PlanWeave work without an existing PRD, roadmap, issue set, or strong source plan. Materialize a Plan Package only when the user explicitly asks.
Auto-document insights and discoveries during development sessions. Unlike MEMORY.md (corrective rules from the self-correction-loop skill), the learning log captures organic discoveries: non-obvious bugs, undocumented architecture decisions, performance findings, workarounds, and gotchas. Stored at .claude/learning-log.md. Load this skill when Claude discovers something non-obvious, finds a workaround, uncovers an undocumented decision, or when the user asks about "learnings", "discoveries", "gotchas", "what did we learn", or "document this finding".
Structured session ending ritual that captures completed work, pending tasks, and learnings before a session ends. Writes a handoff note to .claude/handoff.md so the next session (or a different developer) can pick up exactly where this session left off. Load this skill when the user signals they're wrapping up, says "let's stop here", "that's all for now", "end of session", "wrap up", "save progress", "handoff", or "I'm done for today".
Create structured meeting minutes with decisions, action items, and follow-up tracking. Use this skill when the user needs to document meetings effectively, track action items, improve meeting productivity, or set up a meeting note system — even if they say 'take notes for this meeting', 'what was decided', 'who's responsible for what', or 'our meetings have no follow-through'.