Loading...
Loading...
Found 52 Skills
Manus-style file planning system for organizing and tracking progress of complex tasks. Creates three files: task_plan.md, findings.md, and progress.md. Use when users request planning, decomposition, or organization of multi-step projects, research tasks, or work requiring more than 5 tool calls. Supports automatic session recovery after /clear. Trigger words: task planning, project planning, create plan, decompose task, multi-step planning, progress tracking, file planning, help me plan, decompose project
Feishu Project (Meego/Meegle) operation tool. Supports functions such as querying and managing work items, node workflow, view querying, personal to-dos, and schedule statistics. Use when user needs to work with Feishu/Lark Meego project management — including querying work items, creating/updating work items, completing workflow nodes, checking views, listing todos, analyzing schedules/workloads, or searching with MQL. Keywords: Feishu Project, meego, meegle, work item, requirement, task, defect, schedule, view, to-do, node.
Analyze competitor repositories with an evidence-based approach. Use this when tracking competitors, creating competitor profiles, or generating competitive analysis. CRITICAL - all analysis must be based on actual cloned code, never assumptions. Triggers include "analyze competitor", "add competitor", "competitive analysis", or "竞品分析".
Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work.
Manage Trello boards, lists, cards, checklists, and team workflows via the Trello API.
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".
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.
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.
Provides a comprehensive status overview of the Conductor project. Use when the user wants to know the current progress, active tasks, next steps, or overall health of the project tracks and plans.
Phase 分割された GitHub Issue ツリーを新規作成するスキル。「イシューツリー作って」「タスクを Phase 別に Issue 化」「Issue ツリーを起票して」で使用。 要件・タスク一覧を受け取り、タスク分解（4h 粒度）→ Phase 分割 → ルート（トラッキング）issue → Phase 親 issue → 子 issue の階層を sub_issues API で紐付け。 phase ラベル付与・ルート issue 本文の Phase 別表生成まで自動化。任意の phase 指定で部分起票にも対応。 ツリーの棚卸し・更新は update-issue-tree、実装消化は implement-issue-tree を参照。
Explore codebase, write spec + battle plan — zero questions, pure code research