Loading...
Loading...
Found 33 Skills
Kanban / task board with columns (To do / In progress / In review / Done), draggable-looking cards, assignee avatars, swimlanes, and a top filter bar. Use when the brief mentions "kanban", "task board", "sprint board", "trello", "看板".
Operating protocol that uses Taskwarrior as the continuity layer across conversations. Grounds every interaction in real task state before acting. Activate on "morning" / "briefing" for daily overview, on "status" / "what's next" for current state, when capturing tasks ("remind me to", "add task", "I need to"), when recovering from stalls, or when executing structured work across projects, repos, and life domains.
Show status of all features in .dev/. Scans feature folders using parallel agents, generates a status report, and offers to archive completed features.
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Insert urgent work as a decimal phase between existing phases, adding mid-milestone work, or creating intermediate phases. Triggers include "insert phase", "add urgent phase", "create decimal phase", "insert between phases", and "urgent work".
Write and maintain an implementation diary capturing what changed, why, what worked, what failed (with exact errors and commands), what was tricky, and how to review and validate. Activates proactively during non-trivial implementation work (new features, bug fixes, refactors, research spikes). Does not activate for trivial tasks like one-line fixes, config tweaks, or quick questions.
Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"
Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during execution — to maintain a faithful, auditable trace of how a research project actually evolved.
Simplified state file management with consolidated FLOW.md (project) and ITEM-XXX.md (per-item) files
State-machine driven orchestrator for structured software development. Invoke when user wants to develop features, fix bugs, or refactor code. Triggers: 'build a feature', 'fix this bug', 'implement', 'develop', 'refactor'.
Generate a status report with KPIs, risks, and action items. Use when writing a weekly or monthly update for leadership, summarizing project health with green/yellow/red status, surfacing risks and decisions that need stakeholder attention, or turning a pile of project tracker activity into a readable narrative.
Deterministic plan lifecycle management via scripts/plan-manager.py CLI. Use when user asks to list, show, create, check, complete, or abandon plans, or when session starts and stale plans need surfacing. Use for "check plans", "what's on our plan", "mark task done", "finish this plan", or "create a plan". Do NOT use for executing plan tasks, modifying plan content directly, or performance/refactoring work unrelated to plan tracking.