Loading...
Loading...
Found 124 Skills
Extract business domain knowledge from a codebase and generate an interactive domain flow graph. Works standalone (lightweight scan) or derives from an existing /understand knowledge graph.
High-performance code intelligence MCP server that indexes codebases into knowledge graphs for structural queries, call traces, and architecture analysis
Gather the smallest set of repository, environment, documentation, and runtime evidence needed before planning or changing code. Use when load-bearing facts are unknown, tracing execution paths, inspecting unfamiliar packages, or resolving codebase contradictions — even if the user does not explicitly say "fable-discover" (e.g. "explore the codebase", "how does this work", "where is this implemented", "find where this route is handled"). Do NOT use when the bounded edit is already known (use fable-execute), for external API/version research (use fable-research), or for running existing test suites (use fable-verify).
Create the OpenSpec specs of behaviour that already exists in the code, so the next change can modify or remove it instead of only adding to it.
Turn a settled plan or decision record into a spec, grounded in the codebase and written to spec/features/<slug>/spec.md.
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding
Investigates a question about a codebase or system and answers it from evidence, without changing anything. Gathers evidence first (git history and blame, CI run logs, tests, ADRs and docs), then uses Five Whys for 'why is X failing / why did X break', a scored placement analysis for 'where should Y live' (module, layer, script, package, CI job, or bounded context), and structured explanation, description, or a decision matrix for how/what/which questions. Checks the question's premise and says what evidence it could not reach. Use when the user says /ask-why, asks 'why is this failing', 'why did this break', 'what was the root cause', 'where does this belong', 'where should this check/code live', or wants a root cause explained for a bug that is already fixed. Read-only: no code is written or changed.
Use when bootstrapping team knowledge from a brownfield codebase — reverse-engineers CDRs for contribution to team-ai-directives adlc branch.
Analyzes codebase against standards and generates refactoring tasks for ring:dev-cycle.
Investigate Problem - analyzes a problem in the codebase and proposes actionable solutions
Technical Design - picks one variant per problem area from the research catalogue, then produces architecture diagrams, interfaces, and data flow. Decisions live here, not in research.
Analyze codebase to design and implement comprehensive test coverage — top-down code analysis, bottom-up test design, edge case focus, existing test audit, and agent team execution