Loading...
Loading...
Found 72 Skills
Execute the implementation plan, track progress in the task backend. Use after planning.
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
Implement approved technical plans phase-by-phase, including code changes, verification, and progress updates directly in the plan file. Use this whenever the user asks to execute a plan, implement from a plan document, continue plan-based work, resume from checked/unchecked tasks, or "do phase 1/2/3" from an implementation plan in `rpi/plans/`, even if they do not explicitly name this skill.
Build a World Code business strategy. This is the hub skill that tracks progress across all seven World Code elements and routes to the next one. Use when someone says "build my world code", "start my business strategy", "world code", "world code start", "business strategy framework", or asks about building a business around their worldview.
This skill should be used when the user requests to "save team", "team save", "save team configuration", or "export team". It reads the configuration from a running team and saves it as a snapshot file to the .team-profiles/ directory for reuse with /team-load.
Systematic progress tracking for skill development. Manages task states (pending/in_progress/completed), updates in real-time, reports progress, identifies blockers, and maintains momentum. Use when tracking skill development, coordinating work, or reporting progress.
Records completed work progress to .trellis/workspace/ journal files after human testing and commit. Captures session summaries, commit hashes, and updates developer index files for future session context. Use when a coding session is complete, after the human has committed code, or to persist session knowledge for future AI sessions.
Compare two security audit reports to track remediation progress and identify new vulnerabilities.
Create a context handoff file, pausing work mid-phase, stopping work temporarily, or creating a checkpoint for session resumption. Triggers include "pause work", "stop work", "create handoff", "save progress", and "pause session".
Check project progress, show context, and route to next action (execute or plan). Triggers include "progress".
Documentation-first task execution with quality checks and progress tracking. Use when working with task lists, implementing features, or executing multi-step work to ensure systematic completion with proper documentation review.
List tasks by directory with progress and visual indicators