agentsclimarketplace

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

  • Design handoff spec

    LuckyOneTwoThree/pm-skill/pm-03-design/skills/design-handoff-spec Skill

    no license6★ repo

    当设计阶段完成需要交付给开发团队时使用。开发交接摘要自动生成,整合页面清单、路由结构、功能需求和待确认项,产出面向开发的交接文档。关键词:设计交接、设计交付、Handoff、开发对接、交付文档。

  • Design prd

    LuckyOneTwoThree/pm-skill/pm-03-design/skills/design-prd Skill

    no license6★ repo

    当需要生成标准化PRD文档时使用。PRD自动生成与管理,基于需求和创意方案生成标准化PRD文档,为后续IA、流程和原型设计提供输入。涵盖PRD-L/S/X三级分层、9节完整结构、4道质量门禁。关键词:PRD生成、产品需求文档、需求文档自动生成、PRD管理、写需求文档、产品文档。

  • Interaction spec

    LuckyOneTwoThree/pm-skill/pm-03-design/skills/interaction-spec Skill

    no license6★ repo

    当需要将用户流程和原型设计转化为完整的交互设计规范时使用。交互设计规范文档自动生成,包含交互状态机、动画规范、手势操作、反馈机制、无障碍交互和异常状态处理。关键词:交互设计规范、交互规范、状态机、动画规范、手势操作、交互反馈、无障碍交互、交互文档、动效规范。

  • Requirements prioritization

    LuckyOneTwoThree/pm-skill/pm-03-design/skills/requirements-prioritization Skill

    no license6★ repo

    当需要对需求进行优先级排序时使用。需求自动评估与排序,基于RICE评分和MoSCoW框架对需求进行优先级排序。执行角色:🤖→👤 AI建议,人类审批。关键词:需求排序、RICE评分、MoSCoW、优先级评估、需求优先级。

  • Tracking plan

    LuckyOneTwoThree/pm-skill/pm-04-metrics-design/skills/tracking-plan Skill

    no license6★ repo

    当需要生成埋点方案时使用。埋点方案自动生成,包含从指标体系反推埋点需求、PRD功能埋点提取、埋点质量检查、PRD一致性校验。关键词:埋点方案、事件设计、属性设计、埋点规范、Tracking Plan、数据采集、加埋点、打点。

  • Growth strategy report

    LuckyOneTwoThree/pm-skill/pm-06-growth/skills/growth-strategy-report Skill

    no license6★ repo

    当需要将增长模式诊断和各环节优化方案汇总为完整可交付的增长策略报告时使用。增长策略报告自动生成,包含增长模式评估、AARRR漏斗诊断、杠杆策略、飞轮模型和执行路线图。关键词:增长策略报告、增长报告、AARRR报告、增长飞轮、增长路线图、增长瓶颈、怎么涨上去、增长计划。

  • Gtm strategy

    LuckyOneTwoThree/pm-skill/pm-06-growth/skills/gtm-strategy Skill

    no license6★ repo

    当需要制定产品上市策略时使用。Go-to-Market策略文档自动生成,包含目标市场定义、上市路径选择、定价与包装策略、渠道与推广计划、上市里程碑与成功指标。关键词:Go-to-Market、GTM策略、上市策略、产品上市、市场进入、发布策略、产品上线、怎么推向市场、上市计划。

  • Product sunset plan

    LuckyOneTwoThree/pm-skill/pm-07-monitoring/skills/product-sunset-plan Skill

    no license6★ repo

    当需要制定产品或功能下线计划时使用。产品下线方案自动生成,包含下线决策评估、用户迁移方案、数据处置策略、时间线和沟通计划。关键词:产品下线、功能下线、产品退役、Sunset、下线方案、用户迁移、数据处置、功能下线、停服。

  • Project planning orchestrator

    LuckyOneTwoThree/pm-skill/pm-08-project/orchestrators/project-planning-orchestrator Skill

    no license6★ repo

    当需要启动新项目或进行项目规划时使用。项目规划指挥官,调度 planning-project-charter、planning-resource、planning-kickoff 子Skill执行。关键词:项目规划、项目宪章、资源规划、Kickoff、项目启动、项目章程、资源分配、立项。

  • Agile sprint planning

    LuckyOneTwoThree/pm-skill/pm-08-project/skills/agile-sprint-planning Skill

    no license6★ repo

    当需要规划Sprint时使用。Sprint Planning自动化,将Product Backlog转化为Sprint Backlog,包含Sprint Goal建议、Story自动选取、工作量估算、容量匹配验证,输出完整的Sprint计划。关键词:Sprint规划、Sprint计划、迭代规划、Story选取、容量匹配、排期、这期做啥。

  • Planning kickoff

    LuckyOneTwoThree/pm-skill/pm-08-project/skills/planning-kickoff Skill

    no license6★ repo

    当需要准备和执行项目Kickoff会议时使用。Kickoff会议自动化,包含会前AI准备(议程生成、背景材料整理、问题清单预准备)、会中人类主持、会后AI处理(纪要生成、行动项提取、跟进提醒设置)。关键词:Kickoff、项目启动、启动会议、行动项、项目启动会、启动会、项目开张。

  • Planning project charter

    LuckyOneTwoThree/pm-skill/pm-08-project/skills/planning-project-charter Skill

    no license6★ repo

    当需要生成项目宪章文档时使用。项目宪章自动生成,将产品背景、战略目标、资源约束转化为正式的项目宪章文档,包含背景、目标与范围、成功标准、利益相关方、初步风险评估、资源需求和时间线。关键词:项目宪章、项目章程、项目目标、项目范围、成功标准、项目章程、项目定义。

  • Planning resource

    LuckyOneTwoThree/pm-skill/pm-08-project/skills/planning-resource Skill

    no license6★ repo

    当需要规划项目资源需求时使用。资源需求自动规划,基于项目范围、技术方案和团队能力数据,自动完成工作量估算、资源类型识别、团队能力匹配、资源冲突检测,输出完整的资源配置方案。关键词:资源规划、资源分配、人力规划、资源需求、容量规划、人手不够、要多少人。

  • Ultra planning

    keithhegit/ultra-orchestration/skills-vnext/ultra-planning Skill

    6★ repo

    Rigid decision-complete planning for Codex Ultra vNext. Use after intake, brainstorming, or OpenSpec bridge whenever work spans multiple files, roles, phases, or risk boundaries and must be turned into review-ready TaskManifest and WorkPackage artifacts with explicit dependencies, owned paths, acceptance checks, retry assumptions, and serial versus parallel execution rules.

  • Ultra review

    keithhegit/ultra-orchestration/skills-vnext/ultra-review Skill

    6★ repo

    Spec and engineering review for Codex Ultra vNext. Use after planning or implementation to check specification fidelity, evidence quality, constraints compliance, regression risk, and whether work should be accepted, rejected back to execution, or escalated back to planning.

  • Autoplan

    keithhegit/ultra-orchestration/skills/autoplan Skill

    6★ repo

    Automatically chain intake, planning, spec review, and plan refinement into one orchestrated planning pass, surfacing only decisions that need explicit user approval. Use when the user wants a fast but disciplined planning workflow.

  • Decision complete planner

    keithhegit/ultra-orchestration/skills/decision-complete-planner Skill

    6★ repo

    Turn a structured intake artifact into a decision-complete plan, task graph, dependency map, owned paths, acceptance checks, expected outputs, and retry assumptions. Use when work spans multiple steps, files, or roles and needs explicit orchestration.

  • Spec review

    keithhegit/ultra-orchestration/skills/spec-review Skill

    6★ repo

    Review plans and work packages for specification completeness, hidden assumptions, dependency gaps, interface risks, and acceptance-check quality. Use after planning and before substantial implementation.

  • Architecture designer

    HK-hub/AgentSkills/architecture-designer Skill

    6★ repo

    Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

    The same file is in 1 other repository

  • Prd to issues

    HK-hub/AgentSkills/prd-to-issues Skill

    6★ repo

    Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.

    The same file is in 3 other repositories

  • Prd to plan

    HK-hub/AgentSkills/prd-to-plan Skill

    6★ repo

    Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

    The same file is in 4 other repositories

  • Product management

    HK-hub/AgentSkills/product-management Skill

    6★ repo

    Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy. Use this skill for product planning, writing PRDs, defining MVPs, or competitive analysis.

    The same file is in 1 other repository

  • Write a prd

    HK-hub/AgentSkills/write-a-prd Skill

    6★ repo

    Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

    The same file is in 3 other repositories

  • Approve plan

    Mozurok/fhorja.dev/.claude/skills/approve-plan Skill

    6★ repo

    Atomically lock IMPLEMENTATION_PLAN.md as the approved execution baseline and stamp TASK_STATE.md with the approval signal. Symmetric counterpart to approve-proposed but for the plan itself, not for arbitrary PROPOSED artifacts. Use when IMPLEMENTATION_PLAN.md has been produced (or revised via self-critique-and-revise) and the user authorizes execution to begin. Do not use when the plan is still draft, when implementation-plan returned NO_OP, when the plan contains [NEEDS CLARIFICATION:] markers, or when revisions are still pending review.

  • Autonomous board

    Mozurok/fhorja.dev/.claude/skills/autonomous-board Skill

    6★ repo

    Read-only board-of-record view for an autonomous-run task (ADR-0044 D7, wos/autonomous-track.md). Renders the run as the spec, the IMPLEMENTATION_PLAN waves and slices, and the TASK_STATE phases mapped to to-do / in-progress / escalated / proposed / done columns, sourced only from the Fhorja task artifacts. No external work tracker; no writes. Use when the maintainer wants a single-glance status of an autonomous run without opening every artifact. Do not use to change state (use sync-task-state), to assess a normal multi-slice task (use where-we-at), or to route the next command (use what-next).

  • Backend system design

    Mozurok/fhorja.dev/.claude/skills/backend-system-design Skill

    6★ repo

    Produce a staff-grade backend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model and storage, API contract, caching, scaling and bottlenecks, reliability and SLOs, security, observability, rollout and migration, trade-offs) for a new service, endpoint, or backend feature, persisted as BACKEND_SYSTEM_DESIGN.md. Capability-routed, not stack-specific; composes with slo-define, performance-budget, api-contract-review, and release-plan rather than duplicating them. Use when a backend service or feature needs an architecture-level design before planning and slicing. Do not use to slice an already-designed change (use implementation-plan), to analyze blast radius (use impact-analysis), to review an API contract in isolation (use api-contract-review), to design the frontend surface (use frontend-system-design), or with no active task folder (run task-init first).

  • Component spec

    Mozurok/fhorja.dev/.claude/skills/component-spec Skill

    6★ repo

    Generate a 15-section component specification from a Figma component using MCP tools (get_design_context, get_screenshot, get_variable_defs). Produces a spec doc matching the COMPONENT_SPEC.md template with anatomy, variants, sizes, states, accessibility, motion, haptics, platform, security, performance, and API sections pre-filled from Figma observations. Use when documenting a design system component. Do not use when the component has no Figma representation or when the spec already exists (edit manually instead).

  • Design spec review

    Mozurok/fhorja.dev/.claude/skills/design-spec-review Skill

    6★ repo

    Review a component or screen implementation against its spec doc for alignment on variants, states, accessibility, tokens, and visual fidelity. Distinct from review-hard (general risk) and repo-consistency-sweep (pattern matching). Activates when a slice's declared Scope touches a design-system button, icon, or component convention file (a shared atom/component under a design-system package) with no cited design-spec-review pass for that change. Use when a design system component or screen has been implemented and you want to verify it matches the documented spec. Do not use when no spec exists (write one first with component-spec or screen-spec).

  • Frontend system design

    Mozurok/fhorja.dev/.claude/skills/frontend-system-design Skill

    6★ repo

    Produce a staff-grade frontend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model, API and interface contract, rendering and delivery, state management, performance budget, accessibility, security, rollout, trade-offs) covering web and mobile, persisted as FRONTEND_SYSTEM_DESIGN.md. The default mode writes the design doc for real work; an --interview mode reframes the same structure for a frontend system-design interview round (RADIO-aligned). Capability-routed, not React-specific. Use when a frontend feature or surface needs an architecture-level design before planning and slicing, or when preparing a system-design interview artifact. Do not use to frame whether the problem is right (use problem-framing), to slice an already-designed change (use implementation-plan), to analyze blast radius (use impact-analysis), to review an API contract in isolation (use api-contract-review), or with no active task folder (run task-init first).

  • Godot scene plan

    Mozurok/fhorja.dev/.claude/skills/godot-scene-plan Skill

    6★ repo

    Plan the Godot scene and node structure for a 2D or 3D game feature before any GDScript is written: the scene tree, node types and responsibilities, autoloads (singletons), signal wiring, the input map, and the resources and sub-scenes to create. Produces GODOT_SCENE_PLAN.md, a design-time plan an MCP-driven editor or a human then builds against. Capability-routed and MCP-agnostic (names no specific server). Consults the per-dimension Godot reference topics. A 3D plan SHALL declare its renderer tier or it is incomplete. Use when a Godot 2D or 3D feature or screen needs its scene architecture decided before implementation. Do not use to frame whether the game idea is right (use problem-framing in its game-design mode), to slice an already-planned build (use implementation-plan), to analyze blast radius of an existing Godot project (use impact-analysis), to verify a running scene (use godot-runtime-verify), or with no active task folder (run task-init first).

  • Image to spec

    Mozurok/fhorja.dev/.claude/skills/image-to-spec Skill

    6★ repo

    Generate a design-system spec from a raw image file (a screenshot, mockup, or captured app screen) when there is no Figma source. Reads the image with vision and emits a COMPONENT_SPEC.md-shaped doc (--component) or a SCREEN_SPEC.md-shaped doc (--screen), auto-detecting the mode when no flag is given. A gated --gameplay mode (ADR-0084, off by default) instead derives a MECHANICS_SPEC.md behavior contract for a 2D game from screenshots, extracted video frames, and playtest notes, with every rule in EARS form tagged observed, assumed, or open. Every observation is marked proposed because an image is an inference source, not a source of truth. Use when you have only an image and want a structured spec the design cluster can consume. Do not use when a Figma node exists (use component-spec or screen-spec), when you want code rather than a spec, or to push the image into Figma (that is generate_figma_design, a separate capability).

  • Implement approved slice

    Mozurok/fhorja.dev/.claude/skills/implement-approved-slice Skill

    6★ repo

    Implement only the approved slice with minimal, explicit, review-friendly changes, then persist execution evidence in slice notes and TASK_STATE.md. The single official execution path of the workflow. Supports an opt-in test-first (TDD) mode, enabled per slice or via --tdd, that writes the failing test before the code (ADR-0063). Use when the task has a valid IMPLEMENTATION_PLAN.md, the current slice is explicitly defined and approved, correctness-critical ambiguity is already resolved, and the files in scope are known well enough to edit safely. Do not use when the task is still in discovery or contract refinement or planning, when unresolved ambiguity still affects correctness, when the slice boundary is still unclear, when the next step is only to sync task memory or close the slice (use sync-task-state or slice-closure), or when the remaining work is a narrow micro-delta anchored to an already-executed slice with the same intent (use implement-slice-complement).

  • Implementation plan

    Mozurok/fhorja.dev/.claude/skills/implementation-plan Skill

    6★ repo

    Define an incremental, reviewable, production-safe implementation plan for the active task and persist it as IMPLEMENTATION_PLAN.md plus a TASK_STATE.md update. Breaks work into the smallest safe slices with objective, exact scope, ordering rationale, key risks, validation approach, exit criteria, and work complexity (LOW/MEDIUM/HIGH) per slice. No code is written. Also runs an annotate-only retrofit mode that backfills per-slice Scope and Depends-on plus an Execution waves section onto an existing in-progress plan so it can adopt implement-fleet, without re-planning. A --spec mode derives slices from a spec or PRD, checking every spec item is covered (ADR-0061). Use when impact is understood enough to plan safely, key boundaries are known, and major factual or decision ambiguity is already resolved. Do not use when the task is still too unclear, when key facts or decisions remain open, or when the current need is to implement an already-approved slice (use implement-approved-slice).

  • Pr feedback ingest

    Mozurok/fhorja.dev/.claude/skills/pr-feedback-ingest Skill

    6★ repo

    Turn PR feedback (Greptile, CI, bots, humans) into a structured traceable backlog aligned with TASK_STATE.md, DECISIONS.md, and IMPLEMENTATION_PLAN.md so the next execution step can be a narrow implement-approved-slice or a small planning touch without losing alignment. Corrective scope only. Use when a PR is open or updated and review feedback exists, you want to map each feedback item to files/slices/task-memory updates before coding, or feedback is mostly corrective (bugs, style, missing tests, wrong field usage) under existing scope. Do not use when feedback requires a new product direction or contract (use post-review-pivot first then replan), no active task folder exists, there is no feedback payload to ingest (paste, export, or link summary), or only TASK_STATE.md drift exists without new PR signals (use state-reconcile or sync-task-state). Gated opt-in modes, off by default: --playtest (ADR-0069) ingests Godot playtest notes; --mcp-pull (ADR-0082) pulls feedback through a vetted MCP.

  • Release plan

    Mozurok/fhorja.dev/.claude/skills/release-plan Skill

    6★ repo

    Design a pre-deploy release and rollout strategy for a change: pick the rollout pattern (feature flag, canary, blue-green, or full progressive delivery) by risk and infra, then specify the exposure ramp, the promotion metric and threshold that advances each step, and the rollback trigger and mechanism. Produces RELEASE_PLAN.md. Use when a change is approaching deploy and needs a deliberate rollout (user-facing, risky, or hard to reverse). Do not use for post-deploy live-signal verification (use post-deploy-verifier, which consumes this plan's promotion metric and rollback mechanism), for the standing pipeline's rollback-existence audit (reserved for the future pipeline-gate-review), or for a trivial fully reversible change with no rollout concern. Stack- and infra-agnostic; it designs the rollout, it does not execute it. A gated --godot-mobile mode (ADR-0069) plans an asymmetric Android and iOS Godot 2D-mobile store ship (export toolchain, preflights, store gotchas), off by default.

  • Screen spec fleet

    Mozurok/fhorja.dev/.claude/skills/screen-spec-fleet Skill

    6★ repo

    Orchestrator-workers variant of screen-spec. Dispatches N Sonnet workers (1 screen each) in parallel to generate per-screen spec docs from Figma frames, then merges SCREEN_MAP.md and routes.md from per-worker partials. Use when screen count >= 6 AND Figma MCP is available AND foundations + SCREEN_MAP exist. Do not use for single screens (use screen-spec), when foundations are missing (use design-bootstrap first), or when frames have not been enumerated yet (caller must supply screen_number+slug+persona+node_id per screen).

  • Screen spec

    Mozurok/fhorja.dev/.claude/skills/screen-spec Skill

    6★ repo

    Generate a screen specification from a Figma frame using MCP tools (get_design_context, get_screenshot). Produces a spec doc matching the SCREEN_SPEC.md template with layout sketch, components used, spacing observed, data dependencies, copy, accessibility notes, interactions, and error states. Use when documenting a specific screen. Do not use when the screen has no Figma frame or when the spec already exists. For 6 or more screens, use screen-spec-fleet. Once screens document raw values, use extract-foundations-from-screens to converge tokens.

  • Task init

    Mozurok/fhorja.dev/.claude/skills/task-init Skill

    6★ repo

    Initialize the official task folder and base task memory inside projects/<client>__<project>/active/YYYY-MM-DD_<task-slug>/. Creates README.md, TASK_STATE.md, SOURCE_OF_TRUTH.md, DECISIONS.md, IMPLEMENTATION_PLAN.md; seeds from PROJECT_CHARTER.md when present; emits a multi-repo ## Repositories section in SOURCE_OF_TRUTH.md when 2+ repos are provided. When a vetted issue-tracker MCP is connected, task-init can also seed the task from a referenced item through a gated, opt-in ingest path, off by default. Use when starting a new task from zero or near-zero, or when no active task folder exists yet for this work item. Do not use when the task folder already exists, when work should resume from existing TASK_STATE.md (use resume-from-state), or when the goal is only to update task memory after progress (use sync-task-state). For a brief with 3 or more independent sub-tasks, use task-init-fleet.

  • Test strategy

    Mozurok/fhorja.dev/.claude/skills/test-strategy Skill

    6★ repo

    Define the smallest set of meaningful tests that protects behavior and reduces regression risk for the active task, then persist as TEST_STRATEGY.md plus a TASK_STATE.md update. Avoids forcing a strategy artifact when it adds no material signal. Detects a Godot 2D-mobile target and routes to GUT or gdUnit4 headless, treating the godot-runtime-verify press-play gate as complementary to the headless suite. Use when the task has a valid implementation plan or a clearly understood behavior under change, the change affects important behavior or contracts or data flow or runtime risk or regression risk, or test choices should be decided before or alongside implementation. Use when scope is tagged or reads as auth, biometric, or runtime-risk with no TEST_STRATEGY.md, even if small. Do not use when the task is still too unclear to know what behavior is changing, the current need is broad discovery or contract resolution, or the task is too small to justify a dedicated test strategy artifact.

  • Spec sync

    chipfighter/coding-discipline/plugins/coding-discipline/skills/spec-sync Skill

    6★ repo

    Use in cross-session work when user-confirmed outcomes, non-goals, hard constraints, or acceptance criteria have not been written back to the current source of truth (spec), or reality conflicts with it enough that following it would be wrong; also use during wrap-up or handoff when a source of truth should exist but does not. Edit only the affected original wording; do not keep separate old and new versions. Do not trigger for work that can be completed within one session, local implementation details, verification against existing acceptance criteria, locating the source of truth, or ordinary documentation edits.

  • Api design

    ahgraber/skills/skills/api-design Skill

    6★ repo

    Use when designing, reviewing, or planning REST or GraphQL APIs — endpoint structure, schema design, versioning, error handling, pagination, URI naming, or choosing between REST and GraphQL. Also triggers for OpenAPI spec creation and API contract review.

  • Execute plan

    dbc-oduffy/coordinator-claude/skills/execute-plan Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Goal setting

    dbc-oduffy/coordinator-claude/skills/goal-setting Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Plan delivery audit

    dbc-oduffy/coordinator-claude/skills/plan-delivery-audit Skill

    no license5★ repo

    Triangulate plan-claim / code-reality / review oracles to classify each plan into DELIVERED+REVIEWED / DELIVERED-UNREVIEWED / PARTIAL / IN-FLIGHT / ABANDONED. Run after any crash or 'did we actually finish what we think we finished?' moment.

  • Plan

    dbc-oduffy/coordinator-claude/skills/plan Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Review

    dbc-oduffy/coordinator-claude/skills/review Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Roadmap planning

    dbc-oduffy/coordinator-claude/skills/roadmap-planning Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Shape

    dbc-oduffy/coordinator-claude/skills/shape Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Staff session

    dbc-oduffy/coordinator-claude/skills/staff-session Skill

    no license5★ repo

    An opinionated Claude operating system for PM-led engineering. Planning, enrichment, delegated execution, staged review, ship decisions, durable handoffs.

  • Product primitives

    teambrilliant/dev-skills/skills/product-primitives Skill

    no license5★ repo

    Break down complex products, features, or systems into fundamental primitives and building blocks from a software creator's perspective. Use when starting a new application, designing a large feature, or needing to understand a complex system's moving parts before building. Trigger phrases: "break down X", "decompose this", "what are the primitives", "building blocks of Z", "map the architecture", "what are the moving parts", "analyze this system", or any situation where you need to identify the atomic, reusable capabilities that compose a system. Complements product-thinker (user perspective) with the builder's perspective (system-level connections).

  • Strategic thinker

    teambrilliant/dev-skills/skills/strategic-thinker Skill

    no license5★ repo

    Use for cross-domain strategic reasoning, approach selection, and systems-level analysis. Trigger when the user wants to: think through how to approach a problem, evaluate tradeoffs between architectural or technical approaches, sanity-check a plan or direction, understand second-order effects of a decision, get a holistic view across code/org/time dimensions, or pressure-test assumptions. The core signal is the user asking "what's the right approach?", "think about this", "what am I not seeing?", "sanity check", "tradeoffs", "how should we tackle this?", or any request for multi-level reasoning that spans product, architecture, and organization. Also use when the user needs help deciding which workflow skill to invoke next. NOT for: product/user/business decisions (→ product-thinker), work definition (→ shaping-work), file-level technical planning (→ implementation-planning), writing code, test authoring, or PR review.

  • Working backwards

    teambrilliant/dev-skills/skills/working-backwards Skill

    no license5★ repo

    Claude Code skills for the full dev lifecycle: decompose → shape → plan → implement → QA. Not methodology-specific.

  • Plan

    tercel/code-forge/skills/plan Skill

    no license5★ repo

    Analyze documentation (or a prompt) and generate an implementation plan with task breakdown, TDD steps, and progress tracking. Use when breaking down a feature, creating tasks from docs or requirements, planning implementation work, or turning a spec into actionable steps.

  • Evolution strategy supervisor

    panjose/Co-Scientist/skills/evolution-strategy-supervisor Skill

    5★ repo

    Choose exactly one concrete evolution strategy for the active evolution round.

  • Strategy router

    panjose/Co-Scientist/skills/strategy-router Skill

    5★ repo

    Produce the current `state/STRATEGY_PLAN.json` bundle for configuration, generation, review, evolution, or overview routing.

  • Plan review loop

    augchan42/inkstone/skills/plan-review-loop Skill

    5★ repo

    Run a review loop on an implementation plan — author or locate the plan, get an independent multi-lane review (zero-context executability, grounding against the repo and source spec, task structure), then address findings with judgment. Use when a plan is written and needs adversarial review before execution, or when asked to "review the plan", "check this plan", or "plan review loop". Supports superpowers plans (docs/superpowers/plans/), planning-with-files task_plan.md, and any other plan format; the source spec is reviewed transitively via the traceability lane. For code review loops, see the review-loop plugin.

  • Stakeholder update

    broomva/skills/skills/cadence/stakeholder-update Skill

    5★ repo

    Takes one set of project facts and generates three versions: technical for engineering, business-impact for leadership, and customer-facing for success teams. Use when the user says "stakeholder update", "write an update", "communicate this to different audiences", "translate for leadership", "customer-facing version", or needs to communicate the same information to different audiences.

  • Wealth management

    broomva/skills/skills/finance/wealth-management Skill

    5★ repo

    Wealth management, financial planning, and investment analytics skill. Compounds on finance-substrate for Colombian tax-optimized wealth building. Runs descriptive (portfolio health), predictive (compound growth projections, Monte Carlo), and prescriptive (allocation, rebalancing, tax-efficient withdrawal) analytics. Use when: (1) projecting long-term wealth growth, (2) optimizing asset allocation, (3) running scenario/stress tests on a portfolio, (4) planning tax-efficient contributions or withdrawals, (5) generating a wealth dashboard or net worth timeline, (6) goal-based financial planning (retirement, housing, education). Triggers on: 'wealth management', 'compound interest', 'asset allocation', 'portfolio projection', 'net worth forecast', 'retirement planning', 'investment strategy', 'rebalancing', 'monte carlo', 'financial plan'.

  • Architecture design principles

    broomva/skills/skills/governance/architecture-design-principles Skill

    5★ repo

    Distilled architecture & design principles for building self-service developer platforms, control-plane / data-plane separation, and edge-centralized cross-cutting concerns — drawn from a senior platform engineer's 8-year retrospective on building Atlassian's Envoy-based load-balancing platform (Open Service Broker + Sovereign xDS control plane + AWS infra + sidecar model). Covers the three IaC layers (image / infra / runtime), the template+context pattern for dynamic proxy configuration, forced-migration as an adoption tool, long-term maintenance discipline (churn as a smell, build vs maintain as distinct skills), and the non-technical engineering skills (diplomacy, mentoring vs teaching). Use when: (1) designing a self-service internal developer platform, (2) deciding between native proxy features vs sidecars, (3) introducing or migrating to Envoy / xDS / service mesh, (4) implementing the Open Service Broker spec or any resource-provisioning API, (5) abstracting cloud complexity (AWS CloudFormation, Packer, SaltStack/Ansible/Puppet) behind a developer-friendly API, (6) centralizing cross-cutting concerns (auth, authz, rate limiting, DDoS, access logs) at the edge, (7) planning a fleet-wide migration to new infrastructure, (8) auditing a long-lived codebase for churn / coupling / maintenance burden, (9) onboarding engineers to an existing platform, (10) deciding when to mentor vs train, (11) user says "platform engineering", "control plane", "data plane", "xDS", "Envoy", "service broker", "edge compute", "sidecar", "cross-cutting concerns", "self-service", "internal developer platform", "IDP", "platform migration", "code churn", "long-term maintenance", "mentoring vs teaching".

  • Cross review

    broomva/skills/skills/governance/cross-review Skill

    5★ repo

    bstack P20 — Cross-Model Adversarial Review Gate. The model that wrote the code cannot be the final judge of the code. Before substantive PRs merge, fire a cross-model adversarial gate — different evaluator than writer, anti-slop scoring ≥7/10, max 3 fix rounds, verdict logged in PR. Three strata: (A) Codex CLI cross-vendor for true different-model verdict, (B) fresh-context subagent under devils-advocate brief, (C) composed existing adversarial-review skills always parallel. Use cross-review when: (1) about to push a substantive PR (>200 LOC OR public API OR multi-file OR governance-class), (2) reviewing a draft plan/design before implementation, (3) auditing a feature spec against single-model blind spots, (4) integrating with the /autonomous skill's pre-push gate. Triggers on 'cross-review', 'P20', 'adversarial review', 'anti-slop', 'cross-model gate', 'different evaluator', 'devils advocate gate', 'self-review prohibition'.