Plan & spec
10,724 rows, by stacks then stars
2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid
Plan execution stack mode precheck
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/plan-execution-stack-mode-precheck Skill
0★ repoUse as Pre-Step-0 of `executing-plans` / `subagent-driven-development` / inline-plan-execution when the plan contains `docker compose exec`, SSH commands or other stack-interaction steps. The check distinguishes (a) local-runnable-stack vs (b) remote-only-stack vs (c) hybrid-mode (code-local + live-remote). Prevents mid-execution stop-gates when the plan implicitly assumes "docker compose works here" but secrets/.env.prod, env-files, or services are missing locally. Trigger on phrases like "execute the plan", "executing the plan", "subagent-driven execution start", "docker compose exec in plan steps", "deploy stack vs dev stack", "your-server vs local" mid-plan. Do NOT load for plans without stack interaction (pure-function-only-tasks), for plans where stack-mode is explicitly documented, or for the initial plan-writing phase (writing-plans has its own self-review).
Plan execution state drift precheck
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/plan-execution-state-drift-precheck Skill
0★ repoUse before executing any superpowers/gsd-style implementation plan (`docs/superpowers/plans/*.md`, `.planning/PLAN.md`, `roadmap-phase-*.md`) whose plan-file was written in a previous session — to detect whether tasks have already been implemented (in a parallel session, by a different agent, or by the user) before re-executing them. Trigger on phrases like "start plan execution", "apply executing-plans skill", "gsd-execute-phase", "execute phase", "plan file is from yesterday/last week", "plan written earlier, now executing". Without `git log <base>..HEAD` precheck, completed tasks can be re-implemented inline, wasting significant time. Do NOT load for plans written in the SAME session (no drift possible), plans without git-tracked code targets (pure-documentation phases), or when the user explicitly states "the codebase is at the pre-plan state".
Roadmap phase execution verify first
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/roadmap-phase-execution-verify-first Skill
0★ repoCaptures a pattern from a Phase-A execution session: when executing a roadmap phase from a knowledge vault that was designed days/weeks ago AND a previous session may have prepared draft artifacts (service maps, status files, execution guides), verify each item against current reality (DB queries, docker inspect, systemctl, filesystem) BEFORE applying changes. Find drift in pre-existing files; document discoveries that turn a routine item into an issue; never check a roadmap item as done just because the roadmap said so. Trigger on phrases like "implement Phase X", "execute roadmap item", "implement Phase A of … consolidation", "item Y from the roadmap", "execute the phase from the vault". Do NOT load for fresh roadmap design (use brain-dump-to-phased-roadmap), for executing a freshly-written task list with no vault history, or for non-vault roadmaps.
Strategic proposal vault persistence check
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/strategic-proposal-vault-persistence-check Skill
0★ repoUse at session-end (or mid-session when about to wrap a strategic discussion) when the session has produced structured strategic content — multi-row tables (priority/effort/value matrices, tool inventories), JSON/data schemas (API responses, config-shapes), multi-step recommendations ("Stage 1:..., Stage 2:..."), 5-category frameworks, or anything that took >10min to structure. Risk: this content lives in the conversation buffer, NOT in persistent knowledge — when context expires the entire structuring effort is lost. Trigger phrases like "session wrap-up", "end of day", "is that in the vault?", "did Claude capture that?", "summarize for later", "remember", "wrap up". Do NOT load for sessions producing only ephemeral content (chat-only, single-file-edit, debug-trace), mid-task while strategic discussion is still active, or when post-session-skill-review is already covering the same scan.
Strategic questions before code touch
Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/strategic-questions-before-code-touch Skill
0★ repoUse when about to start a multi-architecture-decision feature implementation (Phase-X-Vision-Spec, complex refactor, new module that touches 3+ existing modules) AFTER Reality-Inventory but BEFORE first code-touch. Pose 2-4 strategic questions via AskUserQuestion that lock in: (a) scope (atomic-block vs phased), (b) model/algorithm choice when ≥2 valid options exist, (c) persistence-decision (new column vs JSONB vs new table), (d) backward-compat strategy. Each question with 2-4 specific options + Recommended-marker. Trigger on phrases like "start Phase X", "implement Vision-Spec", "build new module for X", "refactor Y", "larger code change", "multiple architecture decisions open". Do NOT load for single-bug-fixes, for tasks with only one reasonable approach, when scope/persistence/model are obvious from existing code, or when user explicitly says "just start".
Timelnapp/skills/skills/consulting-os/consult-pipeline Skill
0★ repoTrigger on "consult pipeline", "cos pipeline", "new prospect workflow", "run engagement pipeline", "build proposal end to end", "resume engagement", "/cos-plan", "/cos-resume". Orchestrates CAPTURE through SUMMARY with mandatory human checkpoints. Invokes existing consult-* and timeln-* skills at each stage — never duplicates Timeln logic. NOT a substitute for single-stage skills when user only wants one artifact.
Timelnapp/skills/skills/thinking-os/timeln-find Skill
0★ repoTrigger on "search my memory", "look up in my memory", "recall from my notes", "second brain", "thinking partner", "what should I learn today", "connect my ideas", "show my knowledge gaps", "build a knowledge graph", "what's in my brain", or any question prefixed with "based on my past data" / "from my knowledge graph". Use for open-ended search, synthesis, and exploration over the user's Timeln memory. NOT for quick mid-call recall (use timeln-quickly), past decisions (use timeln-decided), or weekly planning (use timeln-plan).
Timelnapp/skills/skills/thinking-os/timeln-plan Skill
0★ repoTrigger on "plan my saves", "plan my week from Timeln", "cascade my last X days", "prioritize my recent saves", "what should I do with my saves", "turn my saves into actions", "run the framework cascade", "eisenhower my saves". Use when the user wants to convert recent Timeln captures into a ranked action plan. NOT for quick recall (use timeln-quickly) or open-ended exploration (use timeln-find).
Timelnapp/skills/skills/thinking-os/timeln-quickly Skill
0★ repoTrigger on "quickly: X", "quickly recall X", "what did I say about X", "what did they say about X", "find the quote on X", "remind me -- X", "did [name] mention X", "what was the number for X", "what date did I commit to X". Use when the user needs a one-breath answer mid-call or mid-pitch. NOT for exploration (use timeln-find) or planning (use timeln-plan).
gmarmat/claude-pm-kit/.claude/skills/roadmap Skill
0★ repo[PM Twin] Generate or update product roadmap from PRD phases and feature index.
gmarmat/claude-pm-kit/.claude/skills/stakeholder-update Skill
0★ repo[PM Twin] Generate product status update from recent activity — git history, feature progress, metrics.
ClydeShen/harness-skill/skills/engineering/harness-issues Skill
0★ repoBreak a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices with enforced AC templates, creation gates, and dual output to GitHub Issues + PLAN.md. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
ClydeShen/harness-skill/skills/engineering/harness-prd Skill
0★ repoTurn the current conversation context into a GSD-compatible PRD with WHAT/HOW constraints, optionally writing to .harness/phases/01-discuss/CONTEXT.md. Use when user wants to create a PRD from the current context.
richardkmichael/claude-rodin/skills/refine-plan Skill
0★ repoInterview me about the plan
chenwei791129/agent-skills/skills/buffett-investment-strategy Skill
0★ repoApply Warren Buffett's investment strategy framework derived from 60 years of Berkshire Hathaway shareholder letters (1965-2024) and 32 years of annual meeting transcripts (1994-2025). Use when: (1) evaluating a stock or business for investment, (2) analyzing competitive advantages or economic moats, (3) assessing management quality, (4) making capital allocation decisions, (5) reviewing portfolio strategy, (6) discussing value investing principles, (7) user mentions Buffett, Berkshire, value investing, moats, intrinsic value, or margin of safety.
pengqianhan/NZ-life-skills/skills/nz-travel-planner Skill
0★ repoNew Zealand travel planning skill — use this whenever someone wants to plan a road trip or multi-day trip in New Zealand, especially in the Auckland Northland / Bay of Islands region. Triggers when the user mentions visiting NZ attractions (Cape Reinga, Bay of Islands, Paihia, Kerikeri, Whangarei, Matakana, Ninety Mile Beach, Te Paki Sand Dunes, Waitangi, etc.), asks for NZ accommodation recommendations or Airbnb searches, wants a NZ itinerary or travel guide, or asks about booking tours and activities in New Zealand. Even if the user just says "help me plan a trip to New Zealand" or "I'm going to Auckland and want to explore north", use this skill.
pengqianhan/NZ-life-skills/skills/travel-planner Skill
0★ repoUniversal travel planning skill for multi-day road trips and city-hopping itineraries anywhere in the world. Use this whenever someone wants to plan a trip to any country or city, find accommodation (Airbnb or hotels) with real-time availability checking, build a day-by-day itinerary, research and book tours or activities, or get a complete clickable travel guide they can use to book everything. Triggers on any travel planning request such as "help me plan a trip to Japan", "road trip in Europe", "weekend in Sydney", "best things to do in Iceland", "find me an Airbnb in Barcelona", or Chinese requests like planning trips to Thailand, Japan, Australia, etc. Even if the user just describes destinations without asking explicitly for a plan, use this skill. Has deep built-in knowledge for New Zealand Northland (references/nz-northland.md) and accumulates examples from past plans.
chris-peterson/sextant/skills/spec-req Skill
0★ repoLook up, trace, and create spec requirements, and bootstrap a new SPEC.md.
chris-peterson/sextant/skills/spec-status Skill
0★ repoRefresh STATUS.md to match current spec coverage — the lightweight, hook-safe ledger writer in the spec-sync family.
chris-peterson/sextant/skills/spec-sync Skill
0★ repoReconcile SPEC.md and the source — full-domain coverage + drift analysis, applied as one-way syncs.
gigayaya/gigachang-skills/skills/scope-research Skill
0★ repoUse when the user explicitly asks to research the scope of a requirement or proposed change against the current codebase — e.g. "research the scope of this requirement", "what would adding X touch in this codebase", "do scope research on this spec", "/scope-research". Surveys the codebase to surface concrete facts about which files/areas a change would touch and the relevant facts about each touchpoint (callers, prior similar changes, current test state, conventions in use, data/interface contracts), with an honest LOC range per touchpoint. Presents facts neutrally — does not assign t-shirt sizes, time estimates, or risk ratings. When unsure about something material, asks the user clarifying questions before writing the report. Manual-trigger only — never auto-invoke. Skip for trivial single-file or one-line changes where research adds no value.
mjcreativelab/mjcreativelab-agent-prompts/skills/smart-issue-plan Skill
0★ repoGitHub Issue の実装計画を作成・更新する。コードベースを分析し、影響範囲・実装手順・リスクを整理して Issue コメントまたは新規 Issue として投稿する。 ユーザーが「計画立てて」「実装計画」「設計して」「#123 の計画」「/smart-issue-plan #123」と言ったら起動する。 smart-issue-resolve(実装着手)とは別物。計画だけ作りたいときに使う。 --codex-review-loop(-cdxrl)を付けると投稿前に Codex 標準レビューループを実施する。 --codex-advs-review-loop(-cdxarl)は Claude=Breaker × Codex=Judge の敵対的レビューループを回す。 --claude-review-loop(-cldrl)は Opus レビュワーエージェント(包括ラウンドのみ観点を G1/G2/G3 の 3 グループに分割し並列起動)による標準計画レビューループ、 --claude-adv-review-loop(-cldarl)は独立 Opus の Breaker × Judge による敵対的計画レビューループを回す(Codex 不要・Claude Code の Workflow ツール前提。利用できない環境はレビュー未実施で degrade)。 認証・個人情報・決済などセキュリティ影響を検出した場合は、フラグ未指定でも敵対的レビューを自動発動する(Codex 不在環境では claude 系で代替)。
mjcreativelab/mjcreativelab-agent-prompts/skills/smart-spec-to-pr Skill
0★ repo「やりたいこと」を起点に、要件明確化 → spec 承認ゲート → Issue 起票 → 既存スキル連鎖(software-architect → smart-issue-plan → smart-issue-resolve)→ PR 作成 の順で進行を管理する薄い conductor スキル(副作用あり: GitHub Issue 起票・コメント投稿)。 各フェーズの中身(設計・計画・実装・レビュー)は既存スキルが持ち、本スキルは進行・受け渡し・ ゲートのみを担う(フェーズロジックを複製しない)。終点は PR 作成で、マージ・デプロイはスコープ外。 AskUserQuestion / Skill ツールに依存する Claude 専用スキル(他エージェントでは動作しない)。 ユーザーが「やりたいことから PR まで通して」「要件を固めて実装まで進めて」「/smart-spec-to-pr」と言ったら起動する。 計画だけなら smart-issue-plan、Issue から実装なら smart-issue-resolve を直接使う(本スキルはその前段の要件明確化から束ねる)。
lsscecilia/skills-for-microservices/ms-spec Skill
no license0★ repoMap the high-level microservice architecture and generate per-service spec .md files that give AI agents full context — owned APIs, DB tables, events, inter-service dependencies, and data flows. Use when user wants to document microservice interactions, generate context files for AI agents, understand service boundaries, or says "ms-spec" or "map my services".
pacho-h/ssep/skills/reviewing-spec-and-policy Skill
0★ repoReviews product specs, requirements docs, RFCs, PRDs, and policy documents from text, markdown, or Figma. Use for completeness, consistency, edge-case coverage, ambiguity, policy conflicts, or compliance gaps. Triggers on "이 기획서 검토해줘", "스펙 리뷰", "정책 검토", "review this PRD", "is this complete?", "이 기획대로 구현하면 빠진게 뭐가 있을까", "스펙 갭", "요구사항 누락", or whenever a Figma URL is shared in a planning context. Triggers even when the requirement reads as a single concise sentence (e.g. "X should default to inactive and be activatable from detail"); concise requirements hide unstated questions about default values for existing data, role/permission interactions, and state-transition edges that a structured audit surfaces in minutes. Reads sources, runs a multi-dimensional review, returns a prioritized gap report. Distinct from brainstorming (generates new designs) and reviewing-design-fidelity (compares impl vs design); this audits an existing artifact.
pacho-h/ssep/skills/using-ssep Skill
0★ repoUse at the start of every conversation that touches a non-trivial code or design task. Establishes the ssep skill-matching matrix (4 specialized skills — reviewing-spec-and-policy, reviewing-design-fidelity, improving-feature-completeness, running-integration-tests) and requires the matrix to be evaluated BEFORE any other action, including clarifying questions, file reads, or implementation. Triggers on any of these signals — Figma URL shared, PRD/RFC/spec text shared, "review", "구현", "검토", "implement", "ship", "production-ready", "polish", "verify", "e2e", "staging" — even when each individual word looks routine, because ssep's most common failure mode is "the task looks small, just do it" rationalization that skips the spec/design/completeness/integration checks the matrix would have flagged. Distinct from superpowers:using-superpowers which sets up generic skill discipline; this one specifically enforces ssep's four-skill matrix so domain-specific reviews are not silently skipped.
zxt6991-source/fitness-agent/plugins/fitness-planner/skills/fitness-planner Skill
no license0★ repoCreate forward-looking training plans from Strava-derived fitness notes already stored in an Obsidian vault. Use when the user wants a realistic next-week or next-two-week plan generated from recent load, consistency, sport mix, and recovery signals in their existing notes.
zxt6991-source/fitness-agent/skills/fitness-planner Skill
no license0★ repoCreate forward-looking training plans from Strava-derived fitness notes already stored in an Obsidian vault. Use when the user wants a realistic next-week or next-two-week plan generated from recent load, consistency, sport mix, and recovery signals in their existing notes.
quanpersie2001/pulse/skills/brainstorming Skill
no license0★ repoUse before feature work only when the design is still unclear — for shaping vague product intent, comparing possible feature shapes, and turning fuzzy requests into a documented, approved spec before exploring or planning begins. Do not use this when the feature intent is already clear and the remaining work is to lock implementation decisions; that belongs to pulse:exploring. Trigger phrases: design, brainstorm, think through, what should we build, help me think, explore options, compare directions, unclear feature shape, vague product request.
quanpersie2001/pulse/skills/planning Skill
no license0★ repoUse after pulse:exploring when locked decisions are ready and the user needs a mode-gated plan with an approved work shape and current-work prep for validation.
Chengyu break whole into parts
evnchn-agentic/chengyu-skills/chengyu-break-whole-into-parts Skill
0★ repoUse when facing a task too large to hold in one piece — decompose into atomic subtasks. Divide-and-conquer in chengyu form. Pairs naturally with subagent dispatch (each part becomes one subagent's job) and with the dispatching-parallel-agents superpower. The decomposition itself is the skill — the parts should each have one clear purpose and a well-defined interface to the others.
evnchn-agentic/chengyu-skills/chengyu-rest-await-the-tired Skill
0★ repoUse when the operator's requirement, the failing test, the stakeholder argument, or any other inputs are STILL IN FLUX and the temptation is to start implementing now "to be ready" — strategic patience while the situation clarifies, rather than burning cycles on work that may need to be redone after the dust settles
Chengyu think thrice before acting
evnchn-agentic/chengyu-skills/chengyu-think-thrice-before-acting Skill
0★ repoUse AFTER first-round planning is complete, to do META-PLANNING — what wasn't planned that should have been? What pitfalls don't surface in the first round due to existing context bias, context rot, plan mode system prompt biases, or other distortions? Triage importance, surface escape routes (subagent assessment, backups, operator ready for ctrl+C, anything). NOT a duplicate of plan mode or common-sense planning — this is the SECOND pass that catches what the first pass missed.
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/blueprint Skill
no license0★ repoTurn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".
The same file is in 4 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/inventory-demand-planning Skill
no license0★ repoCodified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.
The same file is in 3 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/plan-orchestrate Skill
no license0★ repoRead a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.
The same file is in 2 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/product-capability Skill
no license0★ repoTranslate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
The same file is in 2 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/ralphinho-rfc-pipeline Skill
no license0★ repoRFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
The same file is in 7 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/strategic-compact Skill
no license0★ repoSuggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
The same file is in 2 other repositories
goharabbas321/zeoel-framework/.agents/skills/zeoel/skills/zeoel-sprint-planner Skill
no license0★ repoPhase 2: Use this after a PROJECT_BRIEF.md is approved. Gohar decomposes the brief into sprints and assigns tasks to specialized Zeoel agents with their skill bindings.
goharabbas321/zeoel-framework/all-skills/blueprint Skill
no license0★ repoTurn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".
The same file is in 4 other repositories
goharabbas321/zeoel-framework/all-skills/inventory-demand-planning Skill
no license0★ repoCodified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.
The same file is in 3 other repositories
goharabbas321/zeoel-framework/all-skills/plan-orchestrate Skill
no license0★ repoRead a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.
The same file is in 2 other repositories
goharabbas321/zeoel-framework/all-skills/product-capability Skill
no license0★ repoTranslate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes constraints, invariants, interfaces, and unresolved decisions before multi-service work starts. Use when the user needs an ECC-native PRD-to-SRS lane instead of vague planning prose.
The same file is in 2 other repositories
goharabbas321/zeoel-framework/all-skills/ralphinho-rfc-pipeline Skill
no license0★ repoRFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
The same file is in 7 other repositories
goharabbas321/zeoel-framework/all-skills/strategic-compact Skill
no license0★ repoSuggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
The same file is in 2 other repositories
vidit19sharma/neogents/skills/plan Skill
0★ repoRun the DEEP planning flow — relentless requirements interview, then architect produces a reviewable plan artifact in .neo/plans/. Use for new features, ambiguous scope, architectural changes, or when the user says "plan this" or "let's think this through".
qkitzero/kage-bunshin/.claude/skills/plan-project Skill
0★ repoResearch-backed comprehensive project planning. Use when planning a new project or initiative. Triggered by "make a plan", "I want to start a project", "break down tasks", or "create a roadmap".
YoniChechik/claude-code-config/skills/plan Skill
no license0★ repoExplore codebase and create structured implementation plan
senior-sigan/llm-skills/skills/estimation Skill
no license0★ repoEstimate project scope, timeline, and resource requirements using multiple estimation techniques including bottom-up, top-down, and analogous estimation methods for accurate project planning.
senior-sigan/llm-skills/skills/solution-architect Skill
no license0★ repoTransform product requirements into executable technical architecture. Use when users request: (1) Technical/system architecture design, (2) Tech stack selection, (3) Architecture from PRD, (4) Deployment strategy, (5) Architecture review. Provides workflows from requirements to deployment with tech stack templates. Triggers: architecture, tech stack, system design, deployment, infrastructure.
senior-sigan/llm-skills/skills/spec Skill
no license0★ repoInteractive requirements discovery through Socratic dialogue and systematic exploration
gagip/gagip-dev/plugins/common/skills/draft-plan Skill
no license0★ repo개발 전용 Claude Code 플러그인
RainLib/full-stack-skill/.claude/skills/task-breakdown Skill
0★ repo将程序设计拆分为可管理的开发任务单元,定义优先级、依赖和开发顺序。在程序设计之后、单元测试之前使用。
andresnator/agents-orchestrator/skills/characterization-test-scoping Skill
0★ repoTrigger: characterization tests, seams, high-risk refactor planning, test safety planning. Scope high-risk refactor work around tests, seams, containment, and rollback.
andresnator/agents-orchestrator/skills/fable-planning Skill
0★ repoTrigger: deep plan, plan like Fable, planificar a fondo, fable plan. Fable-5-style planning: evidence before opinion, outcome-first selectivity, minimal calibrated questions, explicit edge-case validation, end-to-end verification plan.
andresnator/agents-orchestrator/skills/jira-user-story Skill
0★ repoCreate or refine Jira User Story tickets in Jira Markup. Use when the user wants a user story, story ticket, product capability, end-user outcome, acceptance criteria for a story, developer-ready story, or SDD-ready User Story input.
andresnator/agents-orchestrator/skills/prd-light Skill
0★ repoTrigger: PRD light, quick PRD, lightweight PRD, MVP requirements. Create lightweight PRDs for small features, internal tools, and early ideas.
andresnator/agents-orchestrator/skills/prd Skill
0★ repoTrigger: PRD, product requirements, technical product spec. Create rigorous PRDs for high-stakes, cross-team, regulated, or security-sensitive work.
andresnator/agents-orchestrator/skills/rfc Skill
0★ repoTrigger: RFC, request for comments, technical proposal. Create RFCs for feature designs, engineering changes, trade-offs, alternatives, and open questions.