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

  • Spec delta checker

    Yue-Zhou1/zkcrypto-audit/plugins/core-audit-flow/skills/spec-delta-checker Skill

    3★ repo

    Compare cryptographic code against a reference specification or paper. Use when implementation details look close to a standard but may have drifted in validation, transcript binding, parameter negotiation, or caller obligations.

  • Requirements

    jovd83/restassured-skill/analysis/requirements Skill

    3★ repo

    Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.

  • Auto sync

    jovd83/restassured-skill/coverage_plan/auto-sync Skill

    3★ repo

    Use when Codex needs to keep Rest Assured API coverage plans, requirements mappings, and test-case documentation synchronized as scenarios are added, removed, or renamed.

  • Generation

    jovd83/restassured-skill/coverage_plan/generation Skill

    3★ repo

    Use when Codex needs to generate a Rest Assured API test coverage plan from approved requirements, OpenAPI or Swagger contracts, WSDL analysis, and explicit scope constraints.

  • Review

    jovd83/restassured-skill/coverage_plan/review Skill

    3★ repo

    Use when Codex needs to present a generated Rest Assured API coverage plan to the user, request explicit approval, and block implementation until the scope is confirmed.

  • Stakeholder

    jovd83/restassured-skill/reporting/stakeholder Skill

    3★ repo

    Use when Codex needs to summarize Rest Assured API test execution for non-technical stakeholders in clear business terms instead of raw test runner output.

  • Plan

    ribeirogab/specwright/plugins/sw/skills/plan Skill

    3★ repo

    A multi-host plugin for Claude Code, Codex, and OpenCode. It gives a repository one explicit, change-driven engineering workflow:

  • Imlazy brainstorm

    hnikoloski/imlazy/skills/imlazy-brainstorm Skill

    3★ repo

    For Heavy-tier tasks only — turn ideas into specs through one-question-at-a-time dialogue, present design in sections, write spec doc, hand off to planning skill

  • Imlazy planning

    hnikoloski/imlazy/skills/imlazy-planning Skill

    3★ repo

    Create and execute implementation plans. Two modes — light (5-bullet inline plan) for Standard tier; full (plan doc + subagent-dispatched execution + per-task review) for Heavy tier

  • Imlazy strategic save

    hnikoloski/imlazy/skills/imlazy-strategic-save Skill

    3★ repo

    Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

  • X9 codex delegation

    xonika9/agent-skills/skills/x9-codex-delegation Skill

    3★ repo

    Claude Code only; never use in a Codex session. Use when substantial, well-scoped work should actually be delegated to Codex — «отдай в Codex», «делегируй Codex», «передай эту часть работы в Codex, чтобы распределить лимиты», "use Codex", implementation, migration, codebase analysis, logged-in browser work, UI verification, or a second-opinion review. Do not use for checking or planning subscription quotas without a concrete task, trivial work, choosing between Claude models, or merely drafting a prompt/brief that is not explicitly being sent to Codex.

  • Forge

    coroboros/agent-skills/skills/forge Skill

    3★ repo

    Pre-implementation thinking — research the problem space, weigh approaches with devil's-advocate rigor, decide what's reversible and conventional while surfacing the load-bearing forks for the user, and emit one apex-ready plan. Use whenever a non-trivial task needs thinking, comparison, or decomposition before code — even when the user doesn't say "forge" (e.g. "should we", "what's the best way", "compare", "evaluate", "pros and cons", "think through", "plan this", "break this down", "spec out", "create issues for", "map out the steps"). Produces a Decision by default (terminal — discuss-then-build); promotes to a Spec with prioritized workstreams when the build path is clear. NOT implementation (→ /ultrapex, /apex, or /oneshot).

  • Implementation planner

    Flowerf19/agents-skills/implementation-planner Skill

    3★ repo

    Create or update execution-ready implementation plans from specs, features, bugs, or subsystem goals, grounded in repository evidence.

  • Plan

    Martin-Hausleitner/martins-awesome-skills/skills/software-development/plan Skill

    3★ repo

    Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes/plans/` directory, and do not execute the work.

    The same file is in 1 other repository

  • Senior pm

    mrDesign-ww/vault-os/shell/claude/skills/senior-pm Skill

    3★ repo

    Senior Project Manager for enterprise software, SaaS, and digital transformation projects. Specializes in portfolio management, quantitative risk analysis, resource optimization, stakeholder alignment, and executive reporting. Uses advanced methodologies including EMV analysis, Monte Carlo simulation, WSJF prioritization, and multi-dimensional health scoring. Use when a user needs help with project plans, project status reports, risk assessments, resource allocation, project roadmaps, milestone tracking, team capacity planning, portfolio health reviews, program management, or executive-level project reporting — especially for enterprise-scale initiatives with multiple workstreams, complex dependencies, or multi-million dollar budgets.

    The same file is in 6 other repositories

  • To prd

    mrDesign-ww/vault-os/shell/claude/skills/to-prd Skill

    3★ 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.

    The same file is in 10 other repositories

  • Paper explorer brief zh

    gy910210/hermes-research-skills/skills/paper-explorer-brief-zh Skill

    3★ repo

    【兼容旧入口】旧的简版文献扩展说明。默认改用 literature-scout-zh,并以 evidence_map 作为正式输出。只有兼容历史调用时才直接使用本 skill。

  • Spec

    angad-kandhari/deliberate/skills/spec Skill

    3★ repo

    Spec-driven feature work. Load when the task involves a PRD, design doc, or solution architecture. Covers finding the spec, extracting problem/persona/success/non-goals, reconciling with architecture, persona-checking the implementation, and keeping the PRD honest when reality diverges.

  • Wayfinding

    lawzava/megapowers/plugins/mega-orchestration/skills/wayfinding Skill

    3★ repo

    Skills, plugins, and hooks that change how coding agents work — Claude Code, Codex, OpenCode, Antigravity. Measured, not vibed.

  • Product planning

    static-var/Keystone/skills/product-planning Skill

    3★ repo

    Software product planning for a concrete software or digital-product initiative whose behavior, UX, user-facing copy, technical direction, scope, or acceptance criteria must be shaped before implementation, or whose approved direction must become a specification.

  • Marketing proposal

    mabzhang/opc-toolkit/skills/marketing-proposal Skill

    3★ repo

    Write client-ready Chinese marketing proposal documents from strategy inputs. Use for formal campaign proposals, pitch documents, marketing plans, launch plans, annual plans, executive summaries, budget/ROI sections and presentation- ready narratives. Trigger for: $marketing-proposal, 营销方案, 策划方案, 提案, 客户提案, pitch deck, proposal writing, 活动策划, 方案文档.

  • Opc proposal

    mabzhang/opc-toolkit/skills/opc-proposal Skill

    3★ repo

    Orchestrate a 4A-grade OPC brand marketing workflow. Use for turning Brand Briefs, Campaign Briefs, WeChat chats, meeting notes, scattered client demands, or one-line marketing requests into a complete Chinese marketing proposal, task order, information-gap list, execution timeline, KOL/media/budget/KPI plan, or coordinated downstream work plan. Trigger for: $opc-proposal, 品牌Brief, CampaignBrief, 提案, 营销全案, 方案, 整合营销, 达人选号, 媒介策略, 投放计划, KOL, KPI, 预算, 渠道, 行业分析, 竞品分析, 消费者洞察, 内容矩阵, 执行任务单.

  • Opc toolkit

    mabzhang/opc-toolkit/skills/opc-toolkit Skill

    3★ repo

    Intelligently route Chinese brand-marketing work to the correct OPC Toolkit workflow and coordinate multiple skills when needed. Use when a request is broad, ambiguous, spans several marketing disciplines, explicitly mentions OPC Toolkit, or needs help choosing among brief analysis, competitor research, consumer insight, campaign planning, social content, platform adaptation, platform specifications, proposal writing, and task decomposition. Trigger for: $opc-toolkit, OPC工具包, 营销工作流, 不知道用哪个技能, 综合营销任务.

  • Social media plan

    mabzhang/opc-toolkit/skills/social-media-plan Skill

    3★ repo

    Build multi-platform social media content strategies, content matrices, monthly calendars, viral frameworks, platform roles and production briefs for Douyin, Xiaohongshu, WeChat, Weibo, Bilibili, video accounts and ecommerce content. Trigger for: $social-media-plan, 社交媒体, 内容运营, 内容矩阵, 内容日历, 种草, 小红书方案, 抖音内容, social media plan, content calendar.

  • Task decomposition

    mabzhang/opc-toolkit/skills/task-decomposition Skill

    3★ repo

    Decompose marketing projects, campaign proposals and strategy outputs into executable task orders with owner roles, dependencies, input/output specs, acceptance criteria, timelines, critical paths and immediate next actions. Trigger for: $task-decomposition, 任务拆解, 执行计划, 怎么做, 分配任务, 项目排期, 下游任务单, task planning, project breakdown.

  • To spec

    barlevalon/skills/catalog/skills/to-spec Skill

    3★ repo

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    The same file is in 11 other repositories

  • To tickets

    barlevalon/skills/catalog/skills/to-tickets Skill

    3★ repo

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in a local file, or native blocking links on a real tracker.

    The same file is in 3 other repositories

  • Create prd

    marco-souza/skills/.agents/skills/create-prd Skill

    no license3★ repo

    Create a Product Requirements Document (PRD) from recent discussions, conversations, or accumulated context. Use when the user wants to formalize requirements, document what was discussed, or create a spec to guide implementation. Do NOT use for technical implementation specs (use SPEC.md from project-files) or for already-implemented features (use CHANGELOG.md).

  • Prd to tasks

    marco-souza/skills/.agents/skills/prd-to-tasks Skill

    no license3★ repo

    Convert a Product Requirements Document (PRD) into a structured tasks.json file with tasks, dependencies, priorities, and estimated effort. Use when a PRD exists and the user wants to break it down into implementable tasks, or says "turn this into tasks," "create issues from the PRD," or "what are the next steps?" Do NOT use when there is no PRD or when the user wants to skip planning and start coding immediately.

  • Project files

    marco-souza/skills/.agents/skills/project-files Skill

    no license3★ repo

    Manage structured communication files (PLAN.md, TODO.md, SPEC.md, etc.) to coordinate work across agents and sessions. Use when starting complex tasks, delegating to subagents, or maintaining project state.

  • Spec plan

    H2Sxxa/spec-coding-skills/skills/spec-plan Skill

    3★ repo

    Turn ambiguous software requests into BDD-style implementation-ready specs with clear scope, constraints, assumptions, acceptance criteria, validation steps, execution guardrails, and an implementation plan. Use this whenever the user is defining requirements, asking for a plan or spec, wants boundaries clarified before coding, mentions acceptance criteria or BDD, or when coding would be risky without first making done explicit.

  • Aa import

    Peeyushmeher/agent-agile/skills/aa-import Skill

    3★ repo

    Use when the user has an existing plan, PRD, or spec document they want brought into this planning system instead of a fresh grill and intake — or invokes /aa-import with a path or description of that document.

  • Aa plan epic

    Peeyushmeher/agent-agile/skills/aa-plan-epic Skill

    3★ repo

    Use when the current epic on the roadmap is done and the next pending epic needs to be sliced into worker-ready story cards, or the user invokes /aa-plan-epic.

  • Long running work planning

    lindoelio/my-agent-skills/long-running-work-planning Skill

    no license3★ repo

    Use this skill when facing complex problems requiring multi-step reasoning, architectural decisions, debugging with unclear root causes, or tasks where the problem scope is uncertain. Invoke even if the user doesn't explicitly mention "reasoning" or "thinking through" — triggers on phrases like "figure out why", "analyze this", "what's the best approach", or when initial attempts fail.

  • Requirement analyzer

    Ow1onp/hermes-agent-skills/skills/define/requirement-analyzer Skill

    3★ repo

    Use when the user presents a vague, ambiguous, or underspecified task. Conducts structured multi-turn dialogue to extract true requirements with ~95% clarity before any code is written.

  • Spec driven dev

    Ow1onp/hermes-agent-skills/skills/define/spec-driven-dev Skill

    3★ repo

    Use when starting a new feature, project, or significant refactor. Writes a comprehensive PRD/spec document before any implementation code, following the "spec-first, code-second" principle.

  • Refined plan mode

    schalkneethling/claude-toolkit/skills/refined-plan-mode Skill

    3★ repo

    Use this skill when the user asks to plan, review, revise, continue, checkpoint, handoff, reset, or execute work using Refined Plan Mode. Also use it for legacy /rpm:start, /rpm:advance, /rpm:review, /rpm:feedback, /rpm:checkpoint, and /rpm:handoff prompts.

  • Autopilot

    momentmaker/kaijutsu/skills/core/autopilot Skill

    3★ repo

    Intent-to-PR pipeline. Describe an outcome in natural language and the system runs the full development pipeline autonomously — brainstorm, spec, plan, build, ship — with multi-agent adversarial review at every artifact stage. Two gates total (post-brainstorm + PR review on GitHub). Cost-capped. Use when the user says "autopilot", "build this end to end", "take this from idea to PR", or invokes /autopilot {intent}.

  • Doc review

    momentmaker/kaijutsu/skills/core/doc-review Skill

    3★ repo

    Universal multi-agent QA gate for markdown artifacts (specs, plans, decision records, RFCs, design docs). Wraps `jutsu swarm doc-review <path>` to run claude / codex / antigravity in parallel with tailored lenses (claude=completeness, codex=implementability, antigravity=consistency), synthesizes into a single review with a disagreement table. Designed to be the final-review pass for any artifact-producing skill (spec-driven-development, planning-and-task-breakdown). Use when the user says "review this spec", "review this plan", "check this RFC", or invokes /doc-review. Prints to stdout; cache + replay supported.

  • Dream

    momentmaker/kaijutsu/skills/core/dream Skill

    3★ repo

    Pre-implementation interrogation. Walks any topic through 8 cognitive lenses to surface hidden assumptions, weak premises, orthogonal angles, temporal decay, and adversarial misuse BEFORE the topic becomes a spec / plan / commit. Use when the user says "what do you think about X?", "should we do X?", "is X worth pursuing?", "let's brainstorm" (note: this is NOT brainstorm — see "vs brainstorm preset" below), or invokes /dream. Composes via jutsu swarm dream for multi-agent matrix mode.

  • Planning and task breakdown

    momentmaker/kaijutsu/skills/core/planning-and-task-breakdown Skill

    3★ repo

    Decompose a spec into a verifiable task list — vertical slices, explicit dependencies, per-task acceptance criteria. Use when the user says "break this down", "task list", "make a plan", "what are the steps", or invokes /plan. End with `jutsu swarm doc-review <plan.md>` to surface gaps before tasks are considered ready for implementation.

  • Refactor plan

    momentmaker/kaijutsu/skills/core/refactor-plan Skill

    3★ repo

    Multi-agent refactor planning — files + goal in, ordered step plan with risk per step out. Wraps `jutsu swarm refactor-plan <path>... --goal "<goal>"` to run claude / codex / antigravity with three angles (claude=architectural decomposition, codex=stepwise risk, antigravity=pattern consistency). Designed to feed into `planning-and-task-breakdown` for execution. Use when the user says "plan this refactor", "how do I restructure", "step plan to extract X", or invokes /refactor-plan.

  • Spec driven development

    momentmaker/kaijutsu/skills/core/spec-driven-development Skill

    3★ repo

    Author a PRD-style spec before writing implementation. Use when the user says "write a spec", "PRD", "design doc", "spec out", "let's plan this", or invokes /spec. Produce a written, reviewable artifact (problem, scope, non-goals, acceptance criteria, open questions). End with `jutsu swarm doc-review <spec.md>` to surface gaps before declaring done.

  • Plan create

    yarlson/yarstack/plugins/yarstack/skills/plan-create Skill

    3★ repo

    Create a final implementation-ready plan from a user brief, settled decisions, and repository evidence. Use when work needs ordered phases, concrete deliverables, dependencies, risks, and validation before coding.

  • Plan update

    yarlson/yarstack/plugins/yarstack/skills/plan-update Skill

    3★ repo

    Make the smallest evidence-backed correction to implementation-plan mechanics. Use when implementation or validation proves incorrect ordering, prerequisites, phase scope, dependencies, steps, or validation gates.

  • Spec update

    yarlson/yarstack/plugins/yarstack/skills/spec-update Skill

    3★ repo

    Make a minimal evidence-backed update to a non-plan product, architecture, API, schema, or behavior contract. Use when implementation or validation cannot determine correctness from the current authoritative contract.

  • Write prd

    arthjean/skills/skills/write-prd Skill

    no license3★ repo

    Fully autonomous research-informed PRD generator. Researches the domain, makes all design decisions based on research + codebase context, then produces a complete PRD with epics, stories, acceptance criteria, quality gates, and a JSON status tracking file. Invoke with /write-prd [feature description].

  • To spec plus

    leek/agent-skills/skills/to-spec-plus Skill

    3★ repo

    Personal collection of agent skills for Claude

  • To tickets plus

    leek/agent-skills/skills/to-tickets-plus Skill

    3★ repo

    Break a plan, spec, or the current conversation into tracer-bullet vertical-slice tickets with explicit blocking edges, approve the breakdown via AskUserQuestion, and publish to the project's issue tracker (GitHub, Linear, or local markdown). Use when the user says "to tickets", "break this into tickets/issues", or a spec needs slicing for implementation.

  • Wayfinder plus

    leek/agent-skills/skills/wayfinder-plus Skill

    3★ repo

    Plan work too big for one agent session as a shared map of decision tickets on the project's issue tracker (GitHub, Linear, or local markdown), then resolve them one per session until the route to the destination is clear. Use when the user says "wayfinder", "chart a map", "work the map", or brings a loose idea too large or foggy to spec in one sitting.

  • Model orchestration

    uzysjung/uzys-agent-harness/.claude/skills/model-orchestration Skill

    3★ repo

    Apply the fixed model-role and thinking-effort policy whenever work is delegated to subagents or a model/effort choice is made: the orchestrator (top-tier model) DIRECTLY sets service direction, reviews plan/spec documents (with multi-persona-review), improves shipped features, and hunts performance/security problems; plan/spec/planning documents are AUTHORED by Opus, which also owns core implementation and V&V, at xhigh or above; repetitive implementation and E2E tests go to Sonnet at high or above — never delegate below those effort floors. Use whenever you are about to spawn an Agent/Task/Workflow worker, pick a model for a subtask, set a thinking/effort level, assign verification, or hand off orchestration because the current model's quota is exhausted. Trigger on "위임해", "에이전트로 돌려", "오케스트레이션", "모델 역할분담", "어떤 모델로", "effort 얼마로", "thinking level", "서브에이전트", or in English "delegate this", "spawn an agent for", "which model should", "route this task", "verify with", "orchestrate". Fire even when the user doesn't name the policy — any delegation decision is in scope.

  • North star

    uzysjung/uzys-agent-harness/.claude/skills/north-star Skill

    3★ repo

    Defines and enforces a project's long-term direction (North Star Statement, metric-as-proxy NSM, strategic Pillars with a module↔pillar map, Will/Won't, 4-gate + priority-order decision heuristics). Use when starting a new project, when scope creep is suspected, or when a non-obvious feature request needs prioritization. Sits one layer above SPEC/PRD — answers 'why and where to', not 'what and how'.

  • Northstar roadmap

    uzysjung/uzys-agent-harness/.claude/skills/northstar-roadmap Skill

    3★ repo

    Read the project's NORTH_STAR / vision doc, measure current state against the goal, then propose a forward direction plus prioritized feature proposals — persisted as a durable roadmap in docs/plans + memory so the plan survives /compact and new sessions. Use when the user asks where the project should go next or wants a backlog grounded in the vision. Fires on the user's real phrasings: "앞으로 어떤 방향으로 개선·발전시킬지 고민해봐", "NORTH.md / NORTH_STAR 보고 나아갈 방향 + 기능 제안", "나아갈 방향 + 기능제안 (수용 → 계획 수립하고 메모리에 기록)", "북극성 정렬 로드맵", as well as the English equivalents: "what direction should we take next", "propose a roadmap / feature backlog from the north star", "plan the next milestones and save it to memory". Not for detecting bugs or auditing current quality (see gap-analysis-e2e / ultracode-service-audit) — this skill DIRECTS forward planning.

  • Spec scaling

    uzysjung/uzys-agent-harness/.claude/skills/spec-scaling Skill

    3★ repo

    Detects when SPEC.md or PRD.md exceeds 300 lines and proposes feature-based splitting with a master route document. Use when SPEC.md grows too large to be effectively used as a single document.

  • Strategic compact

    uzysjung/uzys-agent-harness/.claude/skills/strategic-compact Skill

    3★ repo

    Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.

  • Ultracode service audit

    uzysjung/uzys-agent-harness/.claude/skills/ultracode-service-audit Skill

    3★ repo

    Run a multi-agent, adversarially-verified full-service audit across 7 dimensions (code / UX / scalability / planning+north-star / security / promotion / extensible), separating findings into confirmed / unverified / rejected and producing a priority-ranked, M-numbered milestone roadmap (as many milestones as the findings warrant). Use when the user says "ultracode 전체 서비스 점검", "전체 서비스를 점검하자", "코드·UX·확장성·기획·북극성지표·보안·홍보 문제점을 파악하고 우선순위에 따라 개선", "다차원 서비스 감사", or in English "audit the whole service / full multi-dimensional service audit / find code, UX, scalability, planning, security, and marketing problems and prioritize fixes". The heavyweight superset audit — orchestrate it as a Workflow with fan-out finders and an adversarial verify pass. NOT for a single-artifact prose/README review (use multi-persona-review) or a single-axis gap-vs-benchmark loop (use gap-analysis-e2e) — those are the lighter siblings.

  • Model orchestration

    uzysjung/uzys-agent-harness/templates/skills/model-orchestration Skill

    3★ repo

    Apply the fixed model-role and thinking-effort policy whenever work is delegated to subagents or a model/effort choice is made: the orchestrator (top-tier model) DIRECTLY sets service direction, reviews plan/spec documents (with multi-persona-review), improves shipped features, and hunts performance/security problems; plan/spec/planning documents are AUTHORED by Opus, which also owns core implementation and V&V, at xhigh or above; repetitive implementation and E2E tests go to Sonnet at high or above — never delegate below those effort floors. Use whenever you are about to spawn an Agent/Task/Workflow worker, pick a model for a subtask, set a thinking/effort level, assign verification, or hand off orchestration because the current model's quota is exhausted. Trigger on "위임해", "에이전트로 돌려", "오케스트레이션", "모델 역할분담", "어떤 모델로", "effort 얼마로", "thinking level", "서브에이전트", or in English "delegate this", "spawn an agent for", "which model should", "route this task", "verify with", "orchestrate". Fire even when the user doesn't name the policy — any delegation decision is in scope.

  • North star

    uzysjung/uzys-agent-harness/templates/skills/north-star Skill

    3★ repo

    Defines and enforces a project's long-term direction (North Star Statement, metric-as-proxy NSM, strategic Pillars with a module↔pillar map, Will/Won't, 4-gate + priority-order decision heuristics). Use when starting a new project, when scope creep is suspected, or when a non-obvious feature request needs prioritization. Sits one layer above SPEC/PRD — answers 'why and where to', not 'what and how'.

  • Northstar roadmap

    uzysjung/uzys-agent-harness/templates/skills/northstar-roadmap Skill

    3★ repo

    Read the project's NORTH_STAR / vision doc, measure current state against the goal, then propose a forward direction plus prioritized feature proposals — persisted as a durable roadmap in docs/plans + memory so the plan survives /compact and new sessions. Use when the user asks where the project should go next or wants a backlog grounded in the vision. Fires on the user's real phrasings: "앞으로 어떤 방향으로 개선·발전시킬지 고민해봐", "NORTH.md / NORTH_STAR 보고 나아갈 방향 + 기능 제안", "나아갈 방향 + 기능제안 (수용 → 계획 수립하고 메모리에 기록)", "북극성 정렬 로드맵", as well as the English equivalents: "what direction should we take next", "propose a roadmap / feature backlog from the north star", "plan the next milestones and save it to memory". Not for detecting bugs or auditing current quality (see gap-analysis-e2e / ultracode-service-audit) — this skill DIRECTS forward planning.

  • Spec scaling

    uzysjung/uzys-agent-harness/templates/skills/spec-scaling Skill

    3★ repo

    Detects when SPEC.md or PRD.md exceeds 300 lines and proposes feature-based splitting with a master route document. Use when SPEC.md grows too large to be effectively used as a single document.