Plan & spec
10,741 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
gustavo-meilus/superpipelines/skills/sk-spec-driven-development Skill
5★ repoEstablishes a formal spec→plan→tasks→implement contract for multi-step feature work. Use when authoring multi-step pipelines, building new features, refactoring systems, or when a request is too ambiguous for direct execution and a verified specification must precede implementation.
gustavo-meilus/superpipelines/skills/sk-write-review-isolation Skill
5★ repoEnforces structural separation between the writing agent and the reviewing agent, with Stage 1 (spec compliance) hard-gating Stage 2 (code quality). Use when dispatching a reviewer after a pipeline worker has produced output, when authoring any pipeline step that requires formal verification against a specification, or when implementing a two-stage review loop.
sergeyklay/.agents/.agents/skills/manage-todo Skill
5★ repoRead, update, validate, and report on the project roadmap (TODO.md). Use when asked to add tasks, mark tasks complete, check roadmap status, find what to work on next, triage deferred items into the roadmap, validate TODO.md format, reorder or renumber tasks, or edit milestone descriptions. Also use when the user mentions 'roadmap', 'TODO', 'backlog', 'milestone', 'task list', or asks 'what's next'. Do NOT use for architecture decisions, for changelog entries, for creating implementation plans from specs or managing Issue Trackers (Jira, GitHub, Linear, etc.).
sergeyklay/.agents/.agents/skills/review-arch Skill
5★ repoConduct a principal-level architecture review of a system, specification, diagram, or set of design decisions. Use when asked to review an architecture, evaluate a design, assess coupling/cohesion, check for anti-patterns, audit system boundaries, or produce an Architecture Review Board (ARB) style verdict. Also use when someone says 'review this architecture', 'is this design sound', 'what's wrong with this topology', 'evaluate these tradeoffs', or 'audit this system'. Produces a structured verdict organized around critical risks, significant concerns, observations, strengths, and open questions, grounded in evidence from the codebase and cited against established methodology (ATAM, ISO/IEC 25010, documented anti-pattern catalogues). Do NOT use for line-by-line code review, spec-vs-implementation verification, or PR-level correctness checks.
sergeyklay/.agents/.agents/skills/review-impl Skill
5★ repoReview implementation changes for a given task against architectural standards. Use when reviewing a PR, evaluating recently committed code, assessing whether implementation changes are correct and architecturally sound, or when asked to 'review my changes', 'check this implementation', 'review what I built', 'is this PR ready', or 'audit recent commits'. Accepts a task description, task tracker URL, or issue shorthand (owner/repo#123, #123) as input. Produces a structured review with severity-rated findings, code evidence, and a verdict (Block / Request changes / Approve with notes / Approve). Saves the review to .reviews/Review-impl-{slug}.md. Do NOT use for specification review or spec-vs-implementation verification.
sergeyklay/.agents/.agents/skills/review-spec Skill
5★ repoArchitectural review of a specification or design document, performed before implementation begins. Use whenever a spec or design proposal is in scope and the user asks any quality question — even when not phrased explicitly: 'review this spec', 'evaluate this design', 'is this spec implementable', 'is this ready to build', 'check this architecture proposal', 'review the design for feature X', 'is this design sound', 'what's missing from this spec'. Also triggers when a file under `.specs/` is being evaluated without an existing implementation. Do NOT use for verifying an existing implementation against a spec, reviewing a PR or implementation changes, reviewing an existing system's architecture, or security review.
sergeyklay/.agents/.agents/skills/verify-impl Skill
5★ repoForensic audit of an implementation against its authoritative specification. Use whenever a specification document and an implementation are both in scope and the user asks any conformance question - even when not phrased explicitly: 'does this code match the spec', 'verify this implementation', 'check spec conformance', 'audit compliance between design and code', 'is the implementation faithful', 'verify spec coverage', 'audit against requirements', 'spec-vs-code'. Also triggers when a file path under `.specs/` is mentioned alongside an implementation. Do NOT use for general code review, specification design review before implementation begins, security review, or architecture review without a spec document.
sergeyklay/.agents/.agents/skills/writing-plans Skill
5★ repoConvert a technical specification, tracker reference, or feature request into a rigorous, atomic, dependency-ordered implementation plan the coder agent executes step-by-step. Use whenever the output is a Markdown plan file under `.plans/`, or when asked to plan, break down work, sequence implementation phases, turn a spec into actionable tasks, write a roadmap, decompose a feature into phases, or convert a `Spec-*.md` into a `Plan-*.md` artifact. Defines phase structure, output-style rules (WHAT not HOW, signatures only, no language-tagged code fences, symbol references over file paths), step anatomy (atomic, file-explicit, verify-gated), per-phase constraint checks, the philosophy-checklist self-gate, and a validation script. Do NOT use for writing the specification itself, writing implementation code, writing tests, code review, or evaluating an existing plan.
sergeyklay/.agents/.agents/skills/writing-specs Skill
5★ repoWrite technical specifications from feature requests, prompts, or tracker references. Use when asked to specify, architect, design, write a spec, define requirements, create a technical specification, analyze a feature request, or produce a specification document. Also use when given a tracker reference (Jira, GitHub issue, Linear, Asana, etc.) and a specification is the expected output. Do NOT use for code review, implementation, implementation planning, or reviewing existing specs. Produces structured specification documents the implementer can build from without further clarification.
IncommensurableHubris/fullstack-director/.agents/skills/02-designer Skill
5★ repoRealize the UX for a sprint — turn the spine's design-intent + the sprint's REQs into a tiered design system, per-screen specs, and a DM-ID manifest, all referencing REQs. The FIRST skill to run the Reconcile step: it challenges docs/spec/design-intent.md through the amendment protocol — fleshing out derived/[NEEDS CLARIFICATION] intent, and flagging where the realization violates a stated intent or the WCAG 2.2 AA floor (a brand color failing contrast is a computed contradiction) — and emits structured amendment rows. Use when the user says 'design sprint N', 'design the UI', 'wireframe the screens', 'build the design system', 'design tokens', or 'how should this look'. Writes docs/design/; appends docs/spec/amendment-log.json; never edits the spine's requirements. Do NOT plan epics/sprints — that is /01-planner. Do NOT design the system architecture, ADRs, or the data model — that is /03-architect.
IncommensurableHubris/fullstack-director/.agents/skills/03-architect Skill
5★ repoRealize the system architecture — turn architecture-constraints + sprint REQs (+ 02's design contract) into a lean arc42/C4 system.md, MADR ADRs, and per-feature specs with gradeable Verification Contracts, all referencing REQs. Second skill to run Reconcile, first via a context-isolated subagent: challenges docs/spec/architecture-constraints.md through the amendment protocol, flagging realization-vs-constraint contradictions and fleshing out forced decisions via the tech-mandate flow (amend the constraint AND record a resolving ADR). Use when the user says 'architect the system', 'system design', 'write an ADR', or 'architect sprint N'. Writes docs/architecture/; appends docs/spec/amendment-log.json; amends architecture-constraints.md only via a gated Tier-2; never touches requirements. Sole ADR-ID allocator. Do NOT plan epics/sprints — that is /01-planner. Do NOT design the UX — that is /02-designer. Do NOT implement — that is /04-builder.
IncommensurableHubris/fullstack-director/.agents/skills/04-builder Skill
5★ repoBuild the sprint slice - turn 03's per-feature specs + Verification Contracts (+ 02/03's contracts, the 01 slice) into a working vertical slice under src/** with tests, then emit the build-handoff: the SOLE seed for the isolated reviewer (05). Sequential - no subagents, no user gate. TDD RED-first. Carries every VC row with an EXECUTED/OBSERVED/INFERRED evidence state + coverage map. A non-amender but honest escalator: surfaces build-time drift (code/test to 03, declaration to 00/05) and HALTs rather than faking a pass. Drives the fix pass: turns reviewer RED tests green and TDDs prose findings for re-review. Use when the user says 'build sprint N', 'implement the features', or 'fix the review findings'. Writes src/** + _artifacts/exports/build-handoff-sprint-NN.md; never edits docs/spec/**, docs/architecture/**, or docs/design/**. Do NOT architect or write ADRs - /03-architect. Do NOT verify or QA - /05-reviewer. Do NOT plan sprints - /01-planner. Do NOT design UX - /02-designer.
IncommensurableHubris/fullstack-director/.agents/skills/05-reviewer Skill
5★ repoVerify the sprint build in isolation - a reviewer spawned FRESH, seeded ONLY with 04's build-handoff + spec-slice paths, checked against the spine's Gherkin + the 02 contract; emits SHIP / FIX REQUIRED / BLOCK + a severity tally + attestation. READ-ONLY: writes only the QA report, attestation, and tests (RED per defect - 05 owns RED, 04 owns GREEN); never edits implementation. Re-derives judgment (EXECUTED/OBSERVED/INFERRED states); SHIP is unreachable while anything is INFERRED or a MUST/P0 REQ is uncovered. A non-amender but honest escalator (code/test to 04, spec to 03, declaration to 00/gate). Use when the user says 'review sprint N', 'verify the build', or 'QA'. Writes docs/quality/qa-report-sprint-NN.md + tests under src/**; never edits src/**, docs/spec/**, docs/architecture/**, or docs/design/**. Do NOT build or fix code - /04-builder. Do NOT refactor - /08-refactor. Do NOT audit security - /07-security. Do NOT plan sprints - /01-planner. Do NOT architect - /03-architect.
IncommensurableHubris/fullstack-director/.agents/skills/08-refactor Skill
5★ repoImprove codebase structure WITHOUT changing behavior - a cross-cutting activity refactoring under a non-negotiable test-oracle safety net and reconciling realization docs LOCALLY. One spine wiring: appends an amendment row only for a DECLARATION contradiction (a mere realization drift is fixed LOCALLY, no amendment). Two modes (assess, sprint N). SEQUENTIAL - no subagents; Reconcile runs INLINE. Use when the user says 'refactor', 'tech debt', 'clean up the code', or 'refactor sprint N'. Writes src/** + docs/refactoring/{health-assessment,refactor-plan,refactor-report}-sprint-NN.md; reconciles docs/architecture/**, docs/design/**, quality-guardrails.md; appends docs/spec/amendment-log.json; amends architecture-constraints.md via gated Tier-2; requests ADR max+1. Do NOT fix bugs or verify - /05-reviewer. Do NOT fix vulnerabilities - /07-security. Do NOT build features - /04-builder. Do NOT re-architect - /03-architect. Do NOT tidy only sprint-modified files - /05's within-sprint pass.
IncommensurableHubris/fullstack-director/.agents/skills/status Skill
5★ repoThe project's read-only 'where am I / what's next' oracle - scans the artifact chain, INTEGRITY-CHECKS the spine, counts the governance blockers 06-release gates on, DERIVES live state, and routes the NEXT COMMAND. READ-ONLY with respect to truth: never edits the spine or realizations; the only writes are two generated views, keeping docs/spec/** byte-identical. SEQUENTIAL - no subagents (a single derive-only read). Graded value: the DETERMINISTIC verdict (PASS, or FAIL naming the REQ-ID), pending/deferred amendment + [NEEDS CLARIFICATION] counts, and the routed next command. Use when the user says 'status', 'where are we', or 'what's next', or at session start. Reads docs/spec/** and the artifact chain + git state. Writes ONLY CLAUDE.md Current State + AGENTS.md. Do NOT plan/design/architect/build/review/ship/secure/refactor - it ROUTES to the owning skill. Do NOT edit the spine to fix findings - an integrity FAIL is REPORTED (repair via /00-discovery), never silently corrected.
UK Planning Data MCP Server from MCPBundles
thinkchainai/mcpbundles/com.mcpbundles/uk-planning MCP server
no license5★ repoSearch UK planning applications, entities, datasets, and conservation areas
VersoXBT/claude-initial-setup/skills/core-workflow/branching-strategy Skill
4★ repoGuide git branching strategies, branch naming, and merge/rebase decisions. Use when the user creates branches, asks about Git Flow vs trunk-based development, discusses merge vs rebase, or is setting up a new repository's branching model.
The same file is in 2 other repositories
josephneumann/claude-corps/skills/deep-plan Skill
4★ repoUse when starting a new feature or idea that needs thorough pre-execution planning. Use instead of calling /product-review, /spec, and review skills individually.
josephneumann/claude-corps/skills/milestone-review Skill
4★ repoIterative review-fix loop for accumulated milestone/branch changes. Runs parallel reviewers, fixes findings autonomously, repeats until clean. Use after multiple tasks merge to a milestone branch, or before merging to main. Invoke with /milestone-review --base-branch main. Supports --dry-run and --max-iterations.
josephneumann/claude-corps/skills/plan-design-review Skill
4★ repoScored design plan review: 7 UI/UX dimensions rated 0-10, explains what would make each a 10, then fixes the plan. Run after /spec for UI-heavy features, or standalone on any plan with UI scope.
josephneumann/claude-corps/skills/plan-eng-review Skill
4★ repoInteractive engineering plan review: architecture, code quality, tests, performance. One issue per question. Run after /spec before implementation, or standalone on any plan.
josephneumann/claude-corps/skills/spec Skill
4★ repoUse when you have an idea, goal, or feature description and need to turn it into an actionable plan with tasks
pinguding/Project-Machine-in-the-loop/skills/ko/jarvis-plan Skill
no license4★ repo작업 소스(Jira 티켓·Confluence/Notion 페이지·기존 문서·사람이 직접 작성)를 plan 문서 + 상세 작업 체크리스트로 만들고, 사람의 승인을 받아 .jarvis/에 기록하는 단발 plan 셋업. 워치가 리뷰할 스펙이 된다. 워치(/jarvis)가 첫 부팅에서 사람이 plan을 켰을 때 1회 호출하거나, "계획 세워줘 / 이걸 체크리스트로 쪼개줘" 요청에 단독으로 쓴다. jarvis는 초안을 잡을 뿐, 저작·승인은 사람이 한다. 제품 코드는 절대 쓰지 않는다 — 사람이 승인한 기획 문서만 쓴다.
kelegele/oh-my-pm/skills/iteration-planning Skill
4★ repo基于效果分析和用户反馈规划下一个产品迭代。当用户规划冲刺、回顾、上线后分析、对待办事项排序、分配团队能力,或决定接下来做什么时使用。每当用户说"规划下一个冲刺"、"我们应该构建什么"、"对待办事项排序"、"回顾"或需要平衡新功能、缺陷和技术债务时激活。
kelegele/oh-my-pm/skills/prd-gen Skill
4★ repo从功能需求生成结构化产品需求文档(PRD)。当用户想要创建 PRD、记录新功能、编写产品规格、形式化用户故事、说"为 X 写 PRD"、需要记录需求、或正在准备产品评审会议时使用。即使没有明确说"PRD",当用户需要包含用户故事、验收标准和成功指标的结构化产品文档时也应激活。
kelegele/oh-my-pm/skills/prioritization Skill
4★ repo使用 RICE、MoSCoW 等框架对功能和计划进行优先级排序。当用户需要对待办事项排序、决定构建什么、对功能排名,或说"给这个排优先级"、"我们应该先构建什么"、"如何对这些排名"时使用。即使没有明确说"优先级排序",当用户正在决定接下来做什么或对竞争项目进行排名时也应激活。
kelegele/oh-my-pm/skills/quick-prd Skill
4★ repo在一个工作流中生成包含竞品分析的完整 PRD。当用户需要带竞品上下文的 PRD、想要快速记录功能、说"写一个带竞品对比的 PRD"、或需要综合的产品需求文档时使用。当用户提到创建 PRD 并附带竞品研究,或说"分析竞品并写需求"、"快速为 X 写 PRD"时激活。支持 HTML 原型输出格式。
kelegele/oh-my-pm/skills/requirement-review Skill
4★ repo促进需求评审会议和干系人对齐。当用户需要与干系人评审需求、对功能达成一致、运行 PRD 评审,或说"评审这个 PRD"、"获得批准"、"需求评审会议"时使用。即使没有明确说"需求评审",当用户正在准备干系人会议或需要对需求达成一致时也应激活。
kelegele/oh-my-pm/skills/roadmap-planning Skill
4★ repo创建产品路线图,包含里程碑、时间表和战略对齐。当用户需要规划产品方向、创建路线图、定义里程碑、规划发布,或说"创建路线图"、"我们的计划是什么"、"下季度路线图"时使用。即使没有明确说"路线图",当用户正在规划产品时间线、发布或战略方向时也应激活。
YousefNabil-SOC/claude-apex/skills/gs-autoplan Skill
4★ repoAuto-review planning pipeline - runs CEO then design then eng reviews sequentially with auto-decisions. CARL TRIGGERS: autoplan, run the planning pipeline, full plan review, auto plan, plan everything. SOURCE: garrytan/gstack/autoplan, integrated as gs-autoplan on 2026-05-29.
YousefNabil-SOC/claude-apex/skills/gs-plan-ceo Skill
4★ repoCEO/founder-mode strategic plan review - finds the 10-star product hiding inside the request. CARL TRIGGERS: strategic review, ceo review, rethink this, 10-star product, find the bigger product, strategic challenge. SOURCE: garrytan/gstack/plan-ceo-review, integrated as gs-plan-ceo on 2026-05-29.
YousefNabil-SOC/claude-apex/skills/gs-plan-design Skill
4★ repoDesigner-eye plan review - rates each design dimension 0-10 and flags AI slop. CARL TRIGGERS: design plan review, rate this design plan, design critique, design quality check, plan-mode design review. SOURCE: garrytan/gstack/plan-design-review, integrated as gs-plan-design on 2026-05-29.
YousefNabil-SOC/claude-apex/skills/gs-plan-eng Skill
4★ repoEng manager-mode plan review - architecture lock before build. CARL TRIGGERS: engineering review, architecture review, lock the architecture, eng plan review, technical review. SOURCE: garrytan/gstack/plan-eng-review, integrated as gs-plan-eng on 2026-05-29.
YousefNabil-SOC/claude-apex/skills/gs-spec Skill
4★ repoTurn vague intent into a precise, executable spec in five phases. CARL TRIGGERS: write a spec, draft a spec, scope this feature, spec out, requirements doc. SOURCE: garrytan/gstack/spec, integrated as gs-spec on 2026-05-29.
ralvarezdev/ralvaskills/skills/workflows/feature-planner Skill
4★ repoUpstream feature planning — requirement clarification, constraint discovery, design outline, vertical-slice task breakdown ordered by risk. Hands off to grill-with-docs and tdd. Use when starting new feature work from a vague request and no plan exists yet; if a plan or design already exists, use grill-with-docs to stress-test it instead.
ralvarezdev/ralvaskills/skills/workflows/grill-with-docs Skill
4★ repoGrilling session that challenges an existing plan or design against the project's domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when a plan or design already exists and needs stress-testing; if no plan exists yet, use feature-planner first.
dongzhigang13305312738-art/paper-skills/atomic-decomposition Skill
no license4★ repoDecompose research ideas into atomic, self-contained concepts with bidirectional math-code mapping. For each concept, extract the math formula from papers and find code implementations. Use for complex system papers requiring formal grounding.
The same file is in 1 other repository
dongzhigang13305312738-art/paper-skills/experiment-design Skill
no license4★ repoDesign experiment plans with progressive stages — initial implementation, baseline tuning, creative research, and ablation studies. Plan baselines, datasets, hyperparameter sweeps, and evaluation metrics. Use when planning experiments for a research paper.
The same file is in 1 other repository
dongzhigang13305312738-art/paper-skills/research-plan Skill
no license4★ repo科研分析策略规划助手。根据用户的科研分析需求,通过调研顶尖期刊/会议论文的分析方法,制定个性化、可落地的最优分析策略。适用于需要制定实验设计、数据分析流程、技术路线的场景;兼容旧名 make-research-plan 的 prompt 触发。
dongzhigang13305312738-art/paper-skills/research-planning Skill
no license4★ repoDesign research plans and paper architectures. Given a research topic or idea, generate structured plans with methodology outlines, paper structure, dependency-ordered task lists, UML diagrams, and experiment designs. Use when starting a new research project or paper.
The same file is in 1 other repository
design1online/author-it/skills/storybuilder-improvement-plan Skill
4★ repoAI skills for writers who don't want AI writing their novels for them...
escoffier-labs/skillet/skillet/skills/recipe Skill
4★ repoA skillet full of agent skills that actually ship work. Production-tested SKILL.md workflows for audits, security, releases, and handoffs.
MarieLynneBlock/arcanum-artifex/skills/analysis/acceptance-test-plan Skill
no license4★ repoProduces a traceable acceptance test plan with individually numbered test cases. Each test case maps to a source requirement (user story, use case, or FR), specifies preconditions, steps, and expected results, and includes coverage of the happy path, edge cases, and negative scenarios.
MarieLynneBlock/arcanum-artifex/skills/analysis/product-management/breakdown-epic-pm Skill
no license4★ repoPrompt for creating an Epic Product Requirements Document (PRD) for a new epic. This PRD will be used as input for generating a technical architecture specification.
MarieLynneBlock/arcanum-artifex/skills/analysis/product-management/impediment-prioritization Skill
no license4★ repoRanks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritisation formula. Use when someone asks to prioritise, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritisation, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.
MarieLynneBlock/arcanum-artifex/skills/analysis/product-management/prd Skill
no license4★ repoGenerate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.
MarieLynneBlock/arcanum-artifex/skills/analysis/stakeholder-map Skill
no license4★ repoProduces a stakeholder map structured around the classic influence × interest grid (also called a power/interest matrix). It classifies each stakeholder, recommends an engagement strategy per quadrant, and surfaces alignment risks — stakeholders who are high-influence but opposed or unengaged.
MarieLynneBlock/arcanum-artifex/skills/analysis/write-user-story Skill
no license4★ repoProduces a complete, ready-to-groom user story following the standard Atlassian/agile format. It applies the INVEST criteria and the 3 Cs framework (Card, Conversation, Confirmation) to ensure each story is well-scoped, valuable, and testable — not just syntactically correct.
Create github action workflow specification
MarieLynneBlock/arcanum-artifex/skills/development/devops/create-github-action-workflow-specification Skill
no license4★ repoCreate a formal specification for an existing GitHub Actions CI/CD workflow, optimised for AI consumption and workflow maintenance.
MarieLynneBlock/arcanum-artifex/skills/development/test-strategy Skill
no license4★ repoProduces a test strategy document defining what to test, at which layer, with which tools, and to what coverage standard. It applies the test pyramid model, surfaces coverage gaps in existing codebases, and produces a concrete plan — not a generic "write more tests" recommendation.
danielkinneyspears/federal-proposal-skills/skills/developing-teaming-strategy Skill
4★ repoDevelops the teaming strategy for a US Federal pursuit. Use when the user needs a teaming strategy, a partner gap analysis, teammate selection or scoring, workshare planning, teaming agreements or letters of intent, subcontractor data calls, small-business participation or subcontracting-plan input, or teaming OCI screening. Identifies what the prime cannot cover alone and builds a defensible, compliant team.
danielkinneyspears/federal-proposal-skills/skills/developing-win-strategy Skill
4★ repoDevelops the win strategy for a US Federal proposal. Use when the user needs win themes, discriminators, a win strategy, a value proposition, key messages, proposal themes, or ghosting language for a federal bid. Validates discriminators against a value-and-rarity test, builds substantiated win themes that connect customer hot buttons to provable strengths, maps each theme to a Section M evaluation factor, and addresses the team's competitive exposures.
danielkinneyspears/federal-proposal-skills/skills/drafting-proposal-sections Skill
4★ repoDrafts narrative sections of a US Federal proposal from approved storyboards. Use when the user needs to draft, write, or develop proposal sections, technical volume or management volume narrative, a solution approach, or section content for a federal bid. Writes customer-focused, benefit-led narrative that threads the section's win theme, lands its proof points, stays traceable to the compliance matrix, and is organized so a Section M evaluator can score it easily.
danielkinneyspears/federal-proposal-skills/skills/managing-proposal-operations Skill
4★ repoRuns a US Federal proposal as a managed project. Use when the user needs a proposal management plan, a proposal schedule or calendar, a proposal kickoff, volume plan, author assignments or RACI, an action item register, a question log, amendment impact tracking, review logistics, or production planning. Owns the operational backbone that turns the proposal artifacts into a coordinated, on-time, compliant submission.
danielkinneyspears/federal-proposal-skills/skills/outlining-proposals Skill
4★ repoBuilds a compliant annotated outline and storyboards for a US Federal proposal. Use when the user needs a proposal outline, annotated outline, storyboards, a proposal structure, section plans, a page budget, or wants to plan a proposal before drafting. Builds the structure directly from Section L and the compliance matrix, and annotates each section with the requirements it covers, the Section M factors it is scored under, the win themes to thread, proof points, graphics concepts, page allocation, and author.
danielkinneyspears/federal-proposal-skills/skills/planning-capture Skill
4★ repoBuilds and maintains a living capture plan for a US Federal opportunity in the pre-RFP capture phase. Use when the user needs a capture plan, capture strategy, customer call plan, customer engagement or shaping plan, or wants to organize pre-RFP positioning work, intelligence gaps, teaming actions, and capture milestones. Produces a capture plan artifact with assigned, dated action items aimed at raising probability of win before the RFP releases.
Geono/claude-launchpad/plugins/claude-launchpad/skills/launchpad-spec Skill
4★ repoSpec-driven development framework with iterative refinement. Orchestrates feature development from intent to implementation via structured specs and task breakdown. Triggers on /lp:spec, /lp:refine, /lp:clarify, /lp:tasks, /lp:run-task.
Geono/claude-launchpad/plugins/claude-launchpad/skills/launchpad Skill
4★ repoEnd-to-end development pipeline orchestrator. Guides through spec writing, task breakdown, parallelization planning, and multi-agent execution. Chains launchpad-spec, launchpad-plan, and launchpad-run in sequence. Triggers on /launchpad, build this feature, I want to build.
huyngopt1994/infras-kit/infras-kit-plugin/skills/infra-kit.workflow Skill
no license4★ repoTurn an infra ticket into a lightweight spec, implementation plan, task list, and implementation notes (with optional Confluence-ready output).
Story implementation orchestrator
n-n-code/n-n-code-skills/.agents/skills/story-implementation-orchestrator Skill
4★ repoCoordinate the full story-to-plan preparation workflow across user-story-clarifier, story-repo-scout, and story-implementation-planner. Use when a rough ticket needs clarification, repo scouting, implementation planning, packet validation, partial-packet resumption, or downstream skill routing before coding; avoid direct implementation.