Loading...
Loading...
Found 23 Skills
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Design a prospective Scientific Map and scientific architecture before implementation; target code stays read-only.
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from feature-design-assistant output, (2) resuming interrupted work, (3) batch executing tasks. Triggers on 'start implementation', 'run tasks', 'resume'.
Use for tasks that may need brief clarification before implementation but don't warrant a full plan. If clear, dispatches an implementer immediately; if unclear, asks 1-3 questions, proposes an approach, gets approval, then dispatches. No plan file — lighter and faster than nash + stoudemire.
This skill should be used when the user asks to "implement a plan", "execute implementation", "build from plan", "implement feature", or needs to orchestrate execution of an implementation plan with specialized engineering agents.
Implementation workflows and decision trees for ERPNext Client Scripts. Use when determining HOW to implement client-side features: form validations, dynamic UI, server integration, child table logic. Triggers: how do I implement, when to use, which approach, client script workflow, build form logic, make UI dynamic, calculate fields.
Workflow for executing implementation tasks. Use this skill when you need to: (1) Execute a prepared implementation plan (2) Implement tasks sequentially based on dependency resolution (3) For each task: implement → verify → self-review → external review This skill enforces: (a) dependency-based task execution, (b) per-task review cycle.
Execute implementation plans incrementally with verification at each step. Works through numbered sections one at a time, sanity-checks assumptions against the codebase, and stops on inconsistencies. Use when implementing a pre-defined plan document. Triggers on "implement this plan", "execute step 3.1", "resume plan at section 4".
Use when coding standards, security patterns, or project conventions need to be discovered before implementation begins.
Build scoped work from a spec, issue, or conversation.
Implement one accepted, bounded work card with immediate local verification, invariant preservation, and zero scope drift. Use when executing a planned work card, applying a well-defined code change, implementing an isolated function, or performing targeted single-scope edits — even if the user does not explicitly say "fable-execute" (e.g. "implement this card", "write the code for this step", "apply the agreed changes", "build this component"). Do NOT use when new architectural decisions are required (use fable-plan) or when tests are repeatedly failing (use fable-recover).