agentsclimarketplace

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

  • Sdd draft proposal

    andresnator/agents-orchestrator/skills/sdd-draft-proposal Skill

    0★ repo

    Trigger: draft proposal, borrador de propuesta, SDD proposal interview. Interview, then draft an OpenSpec proposal.md; plan-only, write on approval.

  • Sdd draft spec

    andresnator/agents-orchestrator/skills/sdd-draft-spec Skill

    0★ repo

    Trigger: draft spec, borrador de spec, SDD delta spec interview. Interview, then draft delta specs with scenarios; plan-only, write on approval.

  • Sdd draft tasks

    andresnator/agents-orchestrator/skills/sdd-draft-tasks Skill

    0★ repo

    Trigger: draft tasks, borrador de tareas, SDD tasks interview. Draft ordered, verifiable tasks from spec and design; plan-only, write on approval.

  • Generate project plan

    Moliboy5000/.claude/plugins/cache/claude-plugins-official/figma/2.2.78/workflow-skills/generate-project-plan Skill

    no license0★ repo

    Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.

  • Flow spec

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/flow-spec Skill

    no license0★ repo

    NLSpec authoring — structured specification from multi-AI research

  • Skill prd

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-prd Skill

    no license0★ repo

    AI-optimized PRD creation with 100-point scoring framework

  • Skill writing plans

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-writing-plans Skill

    no license0★ repo

    Zero-context implementation plans with bite-sized tasks. Use when: Use when you have a spec or requirements for a multi-step task.. Auto-invoke when user says "plan how to implement X", "create implementation plan", . "break down this feature into tasks".

  • Plan

    Moliboy5000/.claude/plugins/cache/omc/oh-my-claudecode/4.8.2/skills/plan Skill

    no license0★ repo

    Strategic planning with optional interview workflow

  • Notion spec to implementation

    Moliboy5000/.claude/skills/notion-spec-to-implementation Skill

    no license0★ repo

    Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

    The same file is in 5 other repositories

  • Plan ceo review

    Moliboy5000/.claude/skills/plan-ceo-review Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Plan design review

    Moliboy5000/.claude/skills/plan-design-review Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Plan devex review

    Moliboy5000/.claude/skills/plan-devex-review Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Plan eng review

    Moliboy5000/.claude/skills/plan-eng-review Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Plan tune

    Moliboy5000/.claude/skills/plan-tune Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Task queue

    Stoica-Mihai/claude-skills/plugins/opsx-ext/skills/task-queue Skill

    0★ repo

    Use when the user wants new code written or new behavior added that naturally splits into multiple independent changes — "add X and Y and Z", "build the whole auth system", "migrate the service", or "do this task" when the scope clearly spans several discrete pieces. Orchestrates structured codebase exploration, change queue planning, isolated worktree execution per change, and spec verification. Prefer `opsx-ext:task` for single-change requests that don't need a queue or isolated worktrees. Skip for questions, explanations, bug fixes, single-line patches, console.log debugging, version bumps, and /opsx command runs.

  • Housing planning uk

    socreative/my-claude/plugins/housing-planning-uk/skills/housing-planning-uk Skill

    no license0★ repo

    Expert knowledge of UK Housing and Planning law, specifically the Housing and Planning Act 2016. Use this skill when the user asks about UK property law, landlord regulations, planning applications, rogue landlords, banning orders, rent repayment orders, social housing, or compulsory purchase.

  • Testing strategy

    thetruong1099/android-mvi-base-code/.claude/skills/testing-strategy Skill

    no license0★ repo

    Testing patterns for this project. Use when writing ViewModel unit tests with MainDispatcherRule and MockK, UseCase tests mocking repositories, Repository tests with data source mocks, or Compose UI tests with FakeBaseViewModel and TemplateThemePreview. Covers Google Truth assertions and test naming conventions.

  • Implement plan

    bright-room/br-claude-plugins/plugins/dev-workflow/skills/implement-plan Skill

    no license0★ repo

    Issue 上の実装プランまたはローカル Markdown を元にコードを実装する。Issue 番号またはファイルパスを指定する。

  • Update plan

    bright-room/br-claude-plugins/plugins/dev-workflow/skills/update-plan Skill

    no license0★ repo

    会話のコンテキストと Issue コメントのフィードバックを元に、既存の実装プランを更新する。

  • Clarify

    crustacean-dev/knowledge-skills/skills/clarify Skill

    0★ repo

    Adversarial spec reviewer — runs 10 systematic checks against an existing .knowledge/features/<feature>/spec.md to find gaps, vague criteria, missing edge cases, constitution violations, scope leaks, and implementation details that leaked into the spec. Every FAIL comes with a concrete example and a fix proposal. ALWAYS use this skill when the user wants to validate, audit, challenge, stress-test, or review a feature spec before planning or implementation — whether they say "clarify", "clarify <feature>", "review the spec", "is the spec complete", "what's missing", "find gaps", "challenge the spec", "stress test", "audit the spec", "are we missing anything", "check the spec", or any variant asking about spec quality, completeness, or readiness. Also trigger when the user is about to move from spec to plan and wants confidence the spec is tight. This skill reads and updates spec.md ONLY — it does not create new specs (use /spec), produce plans or architecture (use /plan), break down tasks (use /tasks), write code (use /implement), or review implementation code (use /review, /challenge).

  • Implement

    crustacean-dev/knowledge-skills/skills/implement Skill

    0★ repo

    Write code and tests for a single task from .knowledge/features/<feature>/tasks.md. Picks the next TODO task (or a specific TASK-N), reads its acceptance criteria, referenced user stories, plan, architecture, and conventions, then writes exactly the code and tests needed to satisfy the ACs. Updates task status to DONE when complete. Use this skill whenever the user wants to write code for a planned task — trigger phrases include "implement", "implement auth", "implement TASK-3", "build this", "code this task", "start building", "next task", "what's next to implement", "work on TASK-5", "implement the next task", or any variant asking to write code against a task breakdown. Also trigger for casual phrasing like "ok build it", "let's code the first task", "I finished planning, now write the code", or "pick up where we left off". This skill handles ONE task per invocation — it does NOT write specs (/spec), create plans (/plan), break down tasks (/tasks), review code (/review), challenge implementations (/challenge), do general refactoring, or add tests to existing code outside a task context. If the user asks to "add tests" or "refactor" without referencing a task from tasks.md, this skill should NOT trigger.

  • Plan

    crustacean-dev/knowledge-skills/skills/plan Skill

    0★ repo

    Create technical architecture and planning documents. Two modes — project-level (produces .knowledge/architecture.md + .knowledge/conventions.md with directory structure, package dependencies, build pipeline, testing strategy, coding conventions, commit format, CI/CD) and feature-level (produces .knowledge/features/<feature>/plan.md + api/*.d.ts TypeScript contracts with exact data models, integration maps, and architectural decisions). Every decision includes a rejected alternative with rationale. Use this skill whenever the user wants to plan architecture, define conventions, structure a project, design how a feature should be built technically, figure out package layout or module boundaries, establish coding standards, or determine build/test/CI workflows. Trigger on "plan", "plan <feature>", "architecture", "conventions", "how should we build this", "design the system", "structure the project", "what should the technical approach be", "figure out the data model", or any request to make technical decisions before implementation begins. Requires .knowledge/constitution.md to exist — if missing, redirects to /constitution. Does NOT produce specs (user-facing behavior), tasks (implementation breakdown), or code (implementation). Does NOT read or summarize existing documents — it creates new planning artifacts through a structured interview.

  • Review

    crustacean-dev/knowledge-skills/skills/review Skill

    0★ repo

    Code review — check if implementation matches specs, conventions, and constitution. Use this skill ANY time the user wants to verify, check, audit, or review code that has been written. This includes explicit requests like "review", "review TASK-3", "review auth", "code review" AND indirect requests like "check my work", "check the code", "does this match the spec", "does this follow conventions", "is this clean", "sanity check", "look over the code", "did I miss anything", "any violations", "is the implementation correct", "can we merge this", "is TASK-N done", "are there constitution violations", "check test coverage". ALSO trigger after /implement completes to suggest a review. ALSO trigger when user mentions checking code against knowledge files, acceptance criteria, or convention conformity. This skill reads code and knowledge files, then produces a structured ✅/⚠️/❌ report with file:line references — it never modifies code. Do NOT trigger for spec review (/clarify), writing code (/implement), planning (/plan), task breakdown (/tasks), stress testing (/challenge), refactoring without task context, or adding tests outside a task.

  • Spec

    crustacean-dev/knowledge-skills/skills/spec Skill

    0★ repo

    Create or amend feature specifications with typed code examples, verifiable acceptance criteria, and explicit edge cases. Produces .knowledge/features/<feature>/spec.md — the definitive WHAT document for a feature. ALWAYS use this skill when the user wants to define what a feature does before building it, whether they say "spec", "specify", "requirements", "user stories", "acceptance criteria", "what should this do", "define the feature", "expected behavior", "edge cases for", or any variant asking about feature behavior, inputs/outputs, or success criteria. Also trigger when the user wants to amend an existing spec, add user stories, refine acceptance criteria, or define what's in/out of scope for a feature. This skill describes WHAT to build (behavior, contracts, verification) — never HOW (architecture, algorithms, data structures → use /plan), never task breakdowns (→ /tasks), never code (→ /implement), never project principles (→ /constitution).

  • Tasks

    crustacean-dev/knowledge-skills/skills/tasks Skill

    0★ repo

    Break a feature into ordered implementation tasks. Use this skill whenever the user says "tasks", "tasks <feature>", "break this down", "what needs to be built", "implementation order", "task list", "what's next", "story breakdown", or wants to know what to implement and in what order. Also use when the user wants to update task status ("mark TASK-3 done"), reorder tasks, add tasks, split tasks, or check progress on existing tasks. Trigger even for casual phrasing like "what's left to build", "figure out the implementation steps", "create stories for this feature", or "what do I need to build first". Produces .knowledge/features/<feature>/tasks.md from spec.md + plan.md. Does NOT produce specs (/spec), plans (/plan), code (/implement), or review specs (/clarify).

  • Meal plan

    scurry/meals-agent/.claude/skills/meal-plan Skill

    0★ repo

    Use when generating a weekly meal plan for the Meal OS system. Triggered by "/meal-plan" or "plan meals this week" or "weekly meal plan".

  • Markers

    JLugagne/claude-skills/dev/agile-team-v2/skills/markers Skill

    0★ repo

    Use this skill whenever you need the exact format, lifecycle, or strict rules for the agile-team-v2 code markers — `// AC: <criterion>` + `// TODO(impl-<feature-slug>, ac-<NNN>)` + `panic("not implemented")` (inlined by the architect during scaffolding above each scaffolded function body that maps to an acceptance criterion) and `// SCENARIO: <narrative>` + `// TODO(impl-<feature-slug>, scenario-<NNN>)` + `t.Skip("not implemented")` (inlined by the PM in passe 2 inside business test skeletons under `pm_test_territories`). Covers the strict marker format that `check.sh` enforces (kebab-case feature-slug, three-digit zero-padded NNN, exact `ac-` or `scenario-` prefix), the `pm_test_territories` glob block declared in `.architecture/CONVENTIONS.md` (where `// SCENARIO:` markers may live), the seven-step marker lifecycle (architect scaffolds → PM passe 2 → red → green → e2e-tester → reviewer pass 2 → TODO removed when feature done while `// AC:` stays as permanent record), and the marker-based task lookup procedure (`grep -rn TODO(impl-...)` to locate the scaffolded body or test skeleton — replaces v1 TASK.md/TASK-red.md/TASK-green.md/SCAFFOLD.md prose intermediaries). Loaded by every agent that touches markers in any way: architect (writes `// AC:`), PM (writes `// SCENARIO:`), red (locates AC and writes assertions), green (reads AC and removes TODO when done), e2e-tester (locates SCENARIO and writes e2e assertions), reviewer (Pass 2 verifies marker ↔ user-journey alignment), sprint-planner (lists tasks by code marker in SPRINT.md). Bug-detective is the only agent that does not load this skill — it reads `// AC:` from committed code post-mortem without needing the format spec.

  • Tdd pattern

    JLugagne/claude-skills/dev/agile-team-v2/skills/tdd-pattern Skill

    0★ repo

    Use this skill whenever you are running as the `red` or `green` agent on an agile-team-v2 task. Covers the discipline-based spec isolation between red and green (no private TASK*.md files exist; the only handoff is committed code/tests), the in-scope vs out-of-scope rules of the red/green pattern (applies to standard and architectural complexity features only — mechanical maintenance is a mono-agent task), the mono-assistant safeguard when one Claude instance must wear both hats sequentially (commit red first, fresh session before reading green-side material — `check.sh` audits this at sprint review), and the marker-based task lookup procedure (grep for `TODO(impl-<slug>, ac-<NNN>)` to locate the scaffolded body and its sibling test file). Loaded only by `red` and `green`. Other agents (architect, PM, sprint-planner, e2e-tester, reviewer, bug-detective) operate outside the live red/green isolation flow and do not need these rules.

  • Agile project

    JLugagne/claude-skills/dev/agile-team/skills/agile-project Skill

    0★ repo

    Use this skill whenever you are working on a Go project following this agile workflow — features in .features/, sprints in .sprints/, ADRs in .adrs/, global architecture in .architecture/, per-feature ARCHITECTURE.md written by the Architect, tasks under .features/<slug>/tasks/ with scaffolding-first plus red/green triples (TASK.md shared + TASK-red.md + TASK-green.md), spec isolation between paired teammates, dispute arbitration by the sprint-planner, complexity-based agent assignment (scaffolder, red-opus/sonnet/haiku, green-opus/sonnet/haiku, e2e-tester, reviewer), PM and Architect roles for feature definition, and retro-driven sub-sprints for private-helper test coverage. Triggers: mention of sprint planning, feature breakdown, TASK.md / TASK-red.md / TASK-green.md / SCAFFOLD.md, SPRINT.md, REVIEW.md, RETRO.md, Definition of Ready, Definition of Done, blockers, questions, ADRs with revisit flag, dispute files in .disputes/, any of the sprint-planner/product-manager/architect/scaffolder/red-*/green-*/reviewer agents, agent teams, the scaffor tool, or any repository containing .features/ / .sprints/ / .adrs/ / .architecture/ directories. Also triggers for any Go file editing in such a project — all .go reads and edits must go through go-surgeon, never generic Edit/Write/Read. Consult this skill before planning a sprint, before starting any task, before writing a commit, before creating an ADR, before responding to a dispute, or whenever you need to know what artifact goes where.

  • Go product manager

    JLugagne/claude-skills/dev/go-hexagonal/skills/go-product-manager Skill

    0★ repo

    Decomposes a product specification into ordered features with dependencies, tracks progress, and drives sequential execution through the go-hexagonal pipeline. Use when building a full product from a spec document.

  • Climate action planner

    hartmut-ux/ai-bcorp-team-en/skills/climate-action-planner/.claude/skills/climate-action-planner Skill

    0★ repo
  • Climate action planner

    hartmut-ux/ai-bcorp-team-en/skills/climate-action-planner/.codex/skills/climate-action-planner Skill

    0★ repo
  • Climate action planner

    hartmut-ux/ai-bcorp-team-en/skills/climate-action-planner/.kimi/skills/climate-action-planner Skill

    0★ repo
  • Prd taskmaster

    jmech-pepa/pepa-claude-toolkit/skills/prd-taskmaster Skill

    no license0★ repo

    Smart PRD generator with TaskMaster integration. Detects existing PRDs and offers execute/update/replace options. Generates comprehensive technical PRDs optimized for task breakdown, validates with 13 automated checks, and optionally executes tasks autonomously with datetime tracking and rollback support. Use when user requests "PRD", "product requirements", or mentions task-driven development. Defaults to PRD generation with handoff to TaskMaster. Optionally supports autonomous execution with 4 modes.

    The same file is in 1 other repository

  • Night shift

    Sean-Michael/skills/night-shift Skill

    no license0★ repo

    Autonomous unattended workflow with three modes. PLAN: decompose work into a risk-tagged task list agents can execute without you. RUN: headless loop that executes safe tasks, writes scratchpads, produces a DIGEST. AUDIT LOOP: auditor scores the codebase against a spec, executor implements findings, repeats until score threshold is met or a blocker is hit. Trigger on "queue up work", "night shift", "burn usage while I'm away", "audit and fix until done", "grind on this until it passes", or any unattended autonomous execution request.

  • Plan design

    mvdmakesthings/skills/plugins/delivery/skills/plan-design Skill

    no license0★ repo

    Design planning entry point — reads DESIGN.md, CONTEXT.md, and ADRs plus a Linear issue, identifies all UI surfaces that need design, lets you choose which to work through, then for each surface conducts an alignment interview, generates three layout-archetype mockups via OpenAI image generation, lets you pick one, produces an HTML/CSS implementation, and attaches it to the Linear issue. Use when starting design work on any feature, when you need visual options before committing to layout, or any time you want a Linear ticket to carry its own design artifacts.

  • Plan qa

    mvdmakesthings/skills/plugins/delivery/skills/plan-qa Skill

    no license0★ repo

    Test-planning entry point — reads a Linear issue and its acceptance criteria (plus the repo's test conventions if available), then drafts a comprehensive, layer-aware test plan — per-AC scenarios (happy path, edge, negative) each tagged with a test layer and an expected result, the auth roles / fixtures / data setup needed, the visual states to verify, and the regression watch areas. Shows you the draft for approval, then attaches it to the ticket as <issue-id>-test-plan.md so the qa skill can execute against it later. Use this skill whenever you are refining or grooming a ticket, planning QA before implementation, or whenever someone says "/plan-qa", "plan the QA", "write a test plan", "what should we test for this ticket", "QA plan", "test strategy for this issue", or "how do we verify this" — even if they don't say the words "plan-qa".

  • To issues

    mvdmakesthings/skills/plugins/delivery/skills/to-issues Skill

    no license0★ repo

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

  • To prd

    mvdmakesthings/skills/plugins/delivery/skills/to-prd Skill

    no license0★ repo

    Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

  • Gabe debt

    khujta/gabe-suite/skills/gabe-debt Skill

    no license0★ repo

    Architectural decision-debt scanner. Scans SCOPE + PLAN + code + commit history + retrospectives for decisions that were never made explicitly or that silently contradict each other — the kind that compound into complexity until the application breaks under its own weight. Usage: /gabe-debt [brief | dry-run | audit-rules | extract-rules | pattern=Pn | since=<ref> | strict | <file-or-folder>]. Outputs findings to four KDBP targets: .kdbp/DECISIONS.md, .kdbp/SCOPE.md §14, .kdbp/RULES.md, .kdbp/PENDING.md.

  • Gabe myopic

    khujta/gabe-suite/skills/gabe-myopic Skill

    no license0★ repo

    Role-play a short-sighted user with a shallow planning horizon (1 / 1.5 / 2 steps — never 3+) and walk a flow step by step to flag foresight traps (consequences landing 2+ steps later), overwhelm points, recall demands, and no-undo dead-ends. The INVERSE of an expert panel: what would a beginner fail to see coming? Runs 3 horizons at once and reports each one's fatal step. Works on a described workflow, spec, UI code, screenshots, or a live app. Usage: /gabe-myopic [walk|trap|step|fix|horizon] [target]

  • Gabe plan

    khujta/gabe-suite/skills/gabe-plan Skill

    no license0★ repo

    KDBP-aware planning with lifecycle management + tier decision per phase (MVP/enterprise/scale) and optional HTML review artifacts for complex decisions. Usage: /gabe-plan [goal] [--full-catalog] [--html-artifact|--no-html-artifact]

  • Prd taskmaster

    anombyte93/atlas-ai-skills/skills/prd-taskmaster Skill

    0★ repo

    Smart PRD generator with TaskMaster integration. Detects existing PRDs and offers execute/update/replace options. Generates comprehensive technical PRDs optimized for task breakdown, validates with 13 automated checks, and optionally executes tasks autonomously with datetime tracking and rollback support. Use when user requests "PRD", "product requirements", or mentions task-driven development. Defaults to PRD generation with handoff to TaskMaster. Optionally supports autonomous execution with 4 modes.

    The same file is in 1 other repository

  • Planning

    stotihv/skills/skills/planning Skill

    no license0★ repo

    Generate comprehensive plans for new features by exploring the codebase, synthesizing approaches, validating with spikes, and decomposing into beads. Use when asked to plan a feature, create a roadmap, or design an implementation approach.

  • Cofounder

    rvanbaalen/skills/plugins/cofounder/skills/cofounder Skill

    no license0★ repo

    Business co-founder — your critical-thinking partner for prioritization, strategy, and accountability. Use when you want to check in, spar on ideas, review progress, or do focused business work. Type /cofounder to start a session.

  • Drill me

    rvanbaalen/skills/plugins/drill-me/skills/drill-me Skill

    no license0★ repo

    Use whenever the user has a plan, spec, RFC, ticket, design doc, or rough idea they want stress-tested before code is written. Triggers on "drill me", "interview me", "interrogate this plan", "stress test this", "what am I missing", "make sure we're aligned", "poke holes in this", "drill into this", "before I build this..." with an idea attached, or any time non-trivial work is about to start and pre-implementation alignment matters. Walks the design tree one branch at a time, asks one opinionated question per turn with a recommended answer, and explores the codebase instead of asking when the answer is already there. Continues until shared understanding is reached. Use this even when the user doesn't explicitly invoke the skill, as long as the situation matches — pre-implementation drilling is undertriggered by default.

    The same file is in 1 other repository

  • Open markdown

    rvanbaalen/skills/plugins/open-markdown/skills/open-markdown Skill

    no license0★ repo

    Offer to open markdown documents in mdreader after writing them. Trigger this skill whenever you write or create a markdown file that is a plan, spec, design document, architecture doc, implementation guide, proposal, RFC, or any substantive document meant to be read (not just a config snippet or small edit). Also trigger when the user asks to "open", "view", or "preview" a markdown file. Do NOT trigger for trivial edits to existing files (like fixing a typo in a README), code comments, or CLAUDE.md updates.

  • Plan

    rvanbaalen/skills/plugins/pm/skills/plan Skill

    no license0★ repo

    Define milestones, tasks, and estimates. Scales from a quick task to a full project breakdown. Always attaches deadlines, always asks the user for estimates, and journals all changes.

  • Ss spec new

    JasonLo/skill-sommelier/skills/ss-spec-new Skill

    0★ repo

    Draft a language-agnostic service or system specification in the RFC-style used by OpenAI's Symphony spec — RFC 2119 keywords, explicit scope boundaries, goals/non-goals, domain model, configuration contract, state machine, failure model, reference pseudocode, and a conformance checklist. Use when the user wants to write a SPEC.md, formalise a system contract, capture multi-implementation requirements, or turn a design doc into something a porting team could re-implement from scratch. Triggers on "write a spec", "draft a SPEC.md", "service specification", "system contract", "RFC-style spec", "spec the X", "spec this", "make this re-implementable".

  • Jtbd prd frame

    madebynoam/dcode/plugins/dcode/skills/jtbd-prd-frame Skill

    no license0★ repo

    Use when defining a feature, writing a PRD, or scoping work - reframes requirements around the user's job instead of the feature or team that owns it. Use before design or development begins.

    The same file is in 2 other repositories

  • Autonomous agents

    payals/ai-skills-engine/dot_cursor/skills/ai-research/autonomous-agents Skill

    0★ repo

    Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability. This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability. Key insight: compounding error rates kill autonomous agents. A 95% success rate per step drops to 60% b

    The same file is in 3 other repositories

  • Qa test planner

    payals/ai-skills-engine/dot_cursor/skills/ai-research/qa-test-planner Skill

    0★ repo

    Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

    The same file is in 7 other repositories

  • Create plan

    payals/ai-skills-engine/dot_cursor/skills/development/create-plan Skill

    0★ repo

    Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

  • Create plan

    payals/ai-skills-engine/dot_cursor/skills/development/development/create-plan Skill

    0★ repo

    Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.

    The same file is in 5 other repositories

  • Planning with files

    payals/ai-skills-engine/dot_cursor/skills/workflow-automation/planning-with-files Skill

    0★ repo

    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.

    The same file is in 4 other repositories

  • 30x seo content brief

    square-lupus579/30x-seo/skills/30x-seo-content-brief Skill

    0★ repo

    Generate content briefs by analyzing top-ranking SERP results. Extracts common topics, identifies content gaps, and creates actionable briefs for content-writer. Input: target keyword. Output: content brief with must-cover topics + gap opportunities.

    The same file is in 1 other repository

  • 30x seo plan

    square-lupus579/30x-seo/skills/30x-seo-plan Skill

    0★ repo

    SEO strategy planning: competitor analysis, keyword strategy, content calendar, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "content calendar", or "SEO roadmap".

    The same file is in 1 other repository

  • Niko plan

    Texarkanine/a16n/.cursor/skills/shared/niko-plan Skill

    no license0★ repo

    Niko Memory Bank System - Plan Phase - Implementation Planning

    The same file is in 1 other repository

  • Io spec

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-skills-spec-fields/from-claude/.claude/skills/io-spec Skill

    no license0★ repo

    A resourceful skill carrying every optional spec field

  • Manual spec

    Texarkanine/a16n/packages/plugin-claude/test/fixtures/claude-skills-spec-fields/from-claude/.claude/skills/manual-spec Skill

    no license0★ repo

    A manual-invocation skill carrying every optional spec field