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

  • Ux design

    gabriel-f-santos/coding-agents/skills/ux-design Skill

    no license0★ repo

    Turn a product vision into screens and user flows. Use when someone wants to design the UI from a validated product overview — "gera as telas", "desenha as telas dessa feature", "screen design", "user flows", "wireframes", "como vai ser a tela de X", "monta o protótipo de telas". Reads the product discovery brief / PRD (vision, personas, journeys, features), derives the information architecture, maps user flows, writes a screen spec per screen (layout, components, states, actions), and RENDERS them via a connected design tool — using the `pencil` or `figma` skill / a design MCP if available, else degrading to textual wireframes. Writes a findable summary to docs/design/<slug>/summary.md that the implementation plan references. Do not use to validate the problem (product-discovery) or to talk to a specific design tool directly (use the pencil/figma skill) — this orchestrates the design, the tool skills render it.

  • Concise planning

    karim-bhalwani/agent-skills-collection/skills/concise-planning Skill

    0★ repo

    Generate clear, actionable, and atomic checklists for coding tasks with minimal interaction and reasonable assumptions. Use when creating implementation plans, breaking down tasks into steps, generating task checklists, or planning project workflows.

  • Planning with files

    songsunny00/MySkills/BaseSkills/.agents/skills/planning-with-files Skill

    no license0★ repo

    Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.

  • Review prd

    songsunny00/MySkills/CoderSkills/.agents/skills/review-prd Skill

    no license0★ repo

    以开发视角审查产品需求文档,识别需求不清晰、交互场景遗漏、逻辑冲突、异常处理缺失等问题,输出结构化 Excel 报告

  • Review prd

    songsunny00/MySkills/skills/review-prd Skill

    no license0★ repo

    以开发视角审查产品需求文档,识别需求不清晰、交互场景遗漏、逻辑冲突、异常处理缺失等问题,输出结构化 Excel 报告

  • Stakeholder

    jovd83/junit5-skill/reporting/stakeholder Skill

    0★ repo

    Use when Codex needs to summarize JUnit 5 test execution results for non-technical stakeholders in clear business-oriented language instead of raw runner output.

  • Cto

    javalenciacai/develop-skills/.agents/skills/cto Skill

    0★ repo

    Main role orchestrator. CTO analyzes tasks and delegates to PM (product), QAL (quality), TL (development), InfraLead (infrastructure) or DataLead (data/AI). Entry point for all tasks. Use when: (1) User requests involve product strategy, roadmap or UX, (2) Quality testing, security audits or compliance needed, (3) Development, architecture or code implementation required, (4) Infrastructure, CI/CD, databases or deployment tasks, (5) Data pipelines, analytics, AI/ML models or LLM integration, (6) Cross-domain coordination between multiple areas, (7) Any ambiguous request that needs domain analysis and delegation.

  • Pm

    javalenciacai/develop-skills/.agents/skills/pm Skill

    0★ repo

    Product management orchestrator. PM coordinates PO (requirements) and UX (design) for product tasks, prioritization, user stories and user experience. Reports to CTO. Use when: (1) Defining product vision, strategy or roadmap, (2) User stories, requirements or acceptance criteria needed, (3) UI/UX design, wireframes or prototypes required, (4) Product prioritization or backlog management, (5) User research, personas or customer journey mapping, (6) Product documentation like PRDs or product specs, (7) Coordinating between requirements and design teams.

  • Po

    javalenciacai/develop-skills/.agents/skills/po Skill

    0★ repo

    Product Owner. Defines requirements, user stories, acceptance criteria and backlog prioritization. Uses Shape Up methodology. Reports to PM. Use when: (1) Writing user stories or acceptance criteria, (2) Defining product requirements or PRDs, (3) Backlog prioritization or sprint planning, (4) Shape Up methodology (pitches, bets, cycles), (5) Stakeholder requirements gathering, (6) Feature specifications or functional requirements, (7) Story mapping or release planning.

  • Cerebrate

    jppuche/Ignite/_workflow/templates/skills/cerebrate Skill

    0★ repo

    Intelligent reflection on session knowledge. Harvests explicit facts and implicit insights, analyzes through 4 strategic lenses (Confirms, Challenges, Opens, Windows), presents intelligence brief, then persists premium documentation. Use when: end of session, after research, after strategy conversations, or when user says "cerebrate", "consolidate", "reflect", "update docs".

  • Content

    DariuszCiesielski/polish-agent-skills/skills/content/content Skill

    0★ repo

    Pipeline contentowy — pisanie artykułów SEO, briefy, kalendarze, analiza jakości, AI detection. Polskie persony, dual Google+AI optimization, answer-first formatting. Używaj przy "napisz artykuł", "content plan", "brief contentowy", "kalendarz publikacji", "analiza treści", "przepisz artykuł pod SEO", "sprawdź jakość tekstu", "blog post", "content marketing". Auto-aktywacja przy pracy z plikami .md/.mdx w folderze blog/content/posts. NIE używaj do SEO technicznego — od tego jest skill seo.

  • Craig proposal pricing pl

    DariuszCiesielski/polish-agent-skills/skills/sales/craig-proposal-pricing-pl Skill

    0★ repo

    Tworzenie pakietów ofertowych i struktur cenowych dla polskiego SaaS B2B micro-small (deal sizes 299-4999 PLN/mies). Three-tier pricing z anchoring, ROI justification, executive summary, follow-up cadence, rules dyskontowania. Używaj gdy user mówi "przygotuj ofertę", "stwórz pakiet cenowy", "wyceń to", "napisz propozycję dla klienta", "SOW", "ile wziąć za to". Bazuje na metodologii TheCraigHewitt/proposal-pricing zaadaptowanej do polskiego rynku SaaS — usunięto enterprise RFP/SOW/MAP, dodano polski kontekst (faktury VAT, cykle decyzyjne 1-2 tyg, 1 osoba decyzyjna).

  • Book prioritisation

    stephenrogan/csm-skills/skills/book-prioritisation Skill

    0★ repo

    Prioritises a CSM's full book of accounts into action tiers using a weighted scoring model that considers ARR, health, renewal proximity, engagement status, and strategic importance. Produces a ranked list with recommended time allocation. Use when asked to prioritise accounts, rank a portfolio, determine where to focus, triage a book, decide which accounts need attention first, or when a CSM feels overwhelmed and does not know where to start. Also triggers for questions about account prioritisation, portfolio triage, book ranking, time allocation across accounts, or how to decide which accounts matter most this week.

  • Career dev planner

    stephenrogan/csm-skills/skills/career-dev-planner Skill

    0★ repo

    Structures a CS career progression plan from current role to target role by mapping required skills, identifying gaps, defining development milestones, and building a timeline with specific actions. Covers the full CS career ladder from CSM through VP. Use when asked to plan a career path, build a development roadmap, map skills for promotion, structure a career progression plan, or when a CSM wants to be intentional about moving to the next level. Also triggers for questions about CS career progression, promotion readiness, skills for the next level, career planning in customer success, or what it takes to move from CSM to manager to director to VP.

  • Change management advisor

    stephenrogan/csm-skills/skills/change-management-advisor Skill

    0★ repo

    Provides a structured framework for helping customers drive internal adoption of your product within their organisation. Addresses resistance, stakeholder alignment, communication strategy, and phased rollout planning from the CSM's perspective as an external advisor. Use when asked to help a customer with change management, advise on internal adoption strategy, address resistance to product adoption, plan a team rollout, or when adoption is stalling not because of the product but because of the customer's organisational readiness. Also triggers for questions about customer change resistance, internal adoption blockers, rollout planning, or how to help customers get their teams to actually use the product.

  • Escalation brief writer

    stephenrogan/csm-skills/skills/escalation-brief-writer Skill

    0★ repo

    Writes structured escalation documents that get the right people to act on a customer issue. Includes the headline, timeline, customer impact, resolution attempts, specific ask, and commercial context. Use when asked to write an escalation brief, document an escalation, prepare an internal escalation report, structure a request for engineering or product help, or when a customer issue needs to be routed to a team that has no context on the account. Also triggers for questions about escalation documentation, internal issue briefs, cross-functional requests, or how to write an escalation that actually gets acted on.

  • Executive engagement playbook

    stephenrogan/csm-skills/skills/executive-engagement-playbook Skill

    0★ repo

    Framework for when and how to involve executives -- yours and the customer's -- in the account relationship. Covers timing, framing, preparation, and follow-through for executive engagement at renewal, expansion, escalation, and strategic alignment points. Use when asked about executive engagement strategy, when to go high, how to involve leadership, how to prepare for an executive meeting, or when a situation warrants moving beyond the CSM-level relationship. Also triggers for questions about executive sponsorship, VP-level engagement, C-suite involvement, strategic account elevation, or when leadership involvement could unlock an outcome the CSM cannot achieve alone.

  • Goal setting framework

    stephenrogan/csm-skills/skills/goal-setting-framework Skill

    0★ repo

    Structures personal and professional development goals for a CSM using a progression from current capabilities to target role or skill level. Produces measurable milestones with a timeline. Use when asked to set goals, build a development plan, define career objectives, structure professional growth targets, or when a CSM wants to be intentional about their development rather than waiting for opportunities to appear. Also triggers for questions about goal setting, professional development planning, career growth structuring, skill development targets, or how to build a development plan that actually gets followed.

  • Onboarding plan builder

    stephenrogan/csm-skills/skills/onboarding-plan-builder Skill

    0★ repo

    Creates a structured customer onboarding plan with phased milestones, success criteria, timeline, and responsibility assignments. Adapts by segment and complexity. Use when asked to build an onboarding plan, structure a customer kickoff, create an implementation timeline, design a go-live plan, or when a new customer needs a clear roadmap from contract signing to value realisation. Also triggers for questions about customer onboarding structure, implementation planning, kickoff preparation, time-to-value planning, or how to set up a new customer for success from day one.

  • Quarterly planning builder

    stephenrogan/csm-skills/skills/quarterly-planning-builder Skill

    0★ repo

    Helps a CSM build their quarterly plan with portfolio priorities, measurable targets, focus areas, capacity allocation, and development goals. Produces a structured plan that can be shared with management and reviewed at quarter-end. Use when asked to build a quarterly plan, set Q1-Q4 goals, create a portfolio strategy for the quarter, plan the next 90 days, or when a CSM needs to move from reactive week-to-week management to proactive quarterly strategy. Also triggers for questions about quarterly planning, goal setting for a period, portfolio prioritisation for the quarter, or structuring a 90-day plan.

  • Save play designer

    stephenrogan/csm-skills/skills/save-play-designer Skill

    0★ repo

    Creates a structured intervention plan for an at-risk account by identifying the root cause of the risk, designing a targeted response, assigning actions with timelines, and defining what success looks like. Use when asked to build a save play, design a retention intervention, create a rescue plan for an at-risk account, plan a churn prevention strategy, or when an account has been classified as at-risk and needs a dedicated intervention plan. Also triggers for questions about save plays, retention interventions, at-risk account management, churn prevention planning, or how to save a customer who is thinking about leaving.

  • Stakeholder map builder

    stephenrogan/csm-skills/skills/stakeholder-map-builder Skill

    0★ repo

    Builds a structured map of customer stakeholders with roles, influence levels, engagement status, and relationship strategy per contact. Identifies coverage gaps and single-thread risk. Use when asked to map stakeholders, build an org chart, assess relationship coverage, identify single-thread risk, plan stakeholder engagement, or when a CSM needs to understand who matters at an account and where the relationship gaps are. Also triggers for questions about stakeholder mapping, contact assessment, org chart analysis, relationship coverage, multi-threading assessment, or who to engage at a customer account.

  • Stakeholder research prep

    stephenrogan/csm-skills/skills/stakeholder-research-prep Skill

    0★ repo

    Prepares structured background research on a customer contact before a first meeting or engagement. Builds a profile including likely priorities, role-specific concerns, engagement approach, and conversation starters based on their title, function, and seniority level. Use when asked to prepare for a first meeting with a new contact, research a stakeholder, build a contact profile, prepare for an executive conversation, or when meeting someone at a customer account for the first time. Also triggers for questions about stakeholder preparation, first meeting research, contact profiling, or executive meeting prep with someone you have not met before.

  • Success plan creator

    stephenrogan/csm-skills/skills/success-plan-creator Skill

    0★ repo

    Builds a mutual success plan with the customer that defines what success looks like, how it will be measured, who is responsible, and what the timeline is. Produces a shared document that both sides reference throughout the engagement. Use when asked to create a success plan, build a customer outcome framework, define success criteria with a customer, structure mutual goals, or when a CSM needs to align with a customer on what they are trying to achieve together. Also triggers for questions about success planning, outcome definition, customer goal alignment, mutual accountability frameworks, or how to ensure both sides know what success looks like.

  • Territory transition planner

    stephenrogan/csm-skills/skills/territory-transition-planner Skill

    0★ repo

    Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.

  • Week planner

    stephenrogan/csm-skills/skills/week-planner Skill

    0★ repo

    Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.

  • Acceptance criteria design

    planifest/planifest-framework/planifest-framework/external-skills/acceptance-criteria-design Skill

    0★ repo

    Design executable acceptance criteria for approved requirements by converting goals/specs into binary pass/fail checks with observable outcomes. Use when implementation handoff, QA validation, or release decisions need testable criteria for stable `REQ-*`/`NFR-*` baselines; do not use for requirement discovery, prioritization, or sprint slicing.

  • B2b saas pm

    planifest/planifest-framework/planifest-framework/external-skills/b2b-saas-pm Skill

    0★ repo

    Generate a structured Product Requirements Document (PRD) from a product idea or description — covering overview, objectives, target audience, features, user stories, functional/non-functional requirements, success metrics, and timeline.

  • Capacity planning

    planifest/planifest-framework/planifest-framework/external-skills/capacity-planning Skill

    0★ repo

    Analyse server log files to identify patterns, anomalies, and reliability issues — covering error spikes, recurring failures, performance degradation, and actionable improvement recommendations.

  • Content strategy

    planifest/planifest-framework/planifest-framework/external-skills/content-strategy Skill

    0★ repo

    When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

    The same file is in 2 other repositories

  • Db index strategy

    planifest/planifest-framework/planifest-framework/external-skills/db-index-strategy Skill

    0★ repo

    Index strategy workflow for balancing read latency, write amplification, and plan stability on critical query paths. Use when query performance depends on index design trade-offs; do not use for high-level conceptual modeling.

  • Db migration strategy

    planifest/planifest-framework/planifest-framework/external-skills/db-migration-strategy Skill

    0★ repo

    Schema migration strategy workflow for sequencing changes, compatibility windows, and rollback-safe rollout in live systems. Use when schema evolution impacts running services; do not use for static greenfield schemas without deployment constraints.

  • Deployment strategy blue green

    planifest/planifest-framework/planifest-framework/external-skills/deployment-strategy-blue-green Skill

    0★ repo

    Design blue-green deployment strategy with explicit cutover checks, rollback triggers, and state/data compatibility safeguards. Use when release risk requires fast rollback and environment-level switch control; do not use for canary-percentage experimentation policy design.

  • Deployment strategy canary

    planifest/planifest-framework/planifest-framework/external-skills/deployment-strategy-canary Skill

    0★ repo

    Design canary rollout strategy with progressive traffic steps, guardrail metrics, and automated stop/rollback decisions. Use when releases need incremental risk containment and evidence-based promotion gates; do not use for full-environment cutover planning where blue-green is required.

  • Documentation rfc

    planifest/planifest-framework/planifest-framework/external-skills/documentation-rfc Skill

    0★ repo

    Author RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.

  • Feature flag strategy

    planifest/planifest-framework/planifest-framework/external-skills/feature-flag-strategy Skill

    0★ repo

    Feature flag lifecycle governance workflow for safe rollout, blast-radius control, and cleanup discipline. Use when feature rollout needs runtime controls (targeting, staged exposure, kill-switch policy, ownership, and retirement lifecycle) and those rules are not yet explicit; do not use for statistical experiment design and analysis.

  • Free tool strategy

    planifest/planifest-framework/planifest-framework/external-skills/free-tool-strategy Skill

    0★ repo

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    The same file is in 2 other repositories

  • Git branch strategy

    planifest/planifest-framework/planifest-framework/external-skills/git-branch-strategy Skill

    0★ repo

    Define branch topology, lifecycle rules, and merge policy that match team delivery and release risk. Use when branch protection, release/hotfix flow, and merge discipline must be explicit to prevent unsafe history changes; do not use for CI workflow design or application behavior implementation.

  • Kubernetes workload design

    planifest/planifest-framework/planifest-framework/external-skills/kubernetes-workload-design Skill

    0★ repo

    Kubernetes workload design workflow for resource sizing, autoscaling behavior, and safe rollout strategy. Use when workload specs need concrete sizing and resilience decisions to meet reliability/performance targets; do not use for API contract design or requirement prioritization.

  • Launch strategy

    planifest/planifest-framework/planifest-framework/external-skills/launch-strategy Skill

    0★ repo

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

    The same file is in 1 other repository

  • Lead magnets

    planifest/planifest-framework/planifest-framework/external-skills/lead-magnets Skill

    0★ repo

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

    The same file is in 2 other repositories

  • Non functional requirements

    planifest/planifest-framework/planifest-framework/external-skills/non-functional-requirements Skill

    0★ repo

    Quality attribute specification workflow after functional requirements are defined. Use when approved functional requirements need measurable performance/reliability/security/operability/compliance targets before implementation planning; do not use for initial requirement elicitation or sprint task breakdown.

  • Okr planning

    planifest/planifest-framework/planifest-framework/external-skills/okr-planning Skill

    0★ repo

    Writing and running OKRs — objective quality, key result measurability, grading, and check-in cadence; use when setting or reviewing quarterly goals.

  • Okr writing

    planifest/planifest-framework/planifest-framework/external-skills/okr-writing Skill

    0★ repo

    Write effective Objectives and Key Results that align teams, communicate priorities, and drive measurable outcomes — not vanity metrics or activity tracking

  • Performance capacity planning

    planifest/planifest-framework/planifest-framework/external-skills/performance-capacity-planning Skill

    0★ repo

    Performance capacity planning workflow for forecasting demand, defining headroom policy, and preventing saturation-related SLO breaches. Use when traffic growth or workload forecasts require explicit capacity and threshold decisions; do not use for non-performance functional acceptance decisions.

  • Plan ceo review

    planifest/planifest-framework/planifest-framework/external-skills/plan-ceo-review Skill

    0★ repo

    CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)

  • Plan devex review

    planifest/planifest-framework/planifest-framework/external-skills/plan-devex-review Skill

    0★ repo

    Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

  • Plan eng review

    planifest/planifest-framework/planifest-framework/external-skills/plan-eng-review Skill

    0★ repo

    Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

  • Planning and task breakdown

    planifest/planifest-framework/planifest-framework/external-skills/planning-and-task-breakdown Skill

    0★ repo

    Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

    The same file is in 9 other repositories

  • Pricing strategy

    planifest/planifest-framework/planifest-framework/external-skills/pricing-strategy Skill

    0★ repo

    When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

    The same file is in 5 other repositories

  • Project estimation

    planifest/planifest-framework/planifest-framework/external-skills/project-estimation Skill

    0★ repo

    Project estimation workflow for dependency-aware breakdowns and uncertainty-calibrated effort ranges. Use when initiatives need planning-grade estimates with explicit assumptions and confidence ranges; do not use for low-level implementation design details.

  • Requirement elicitation

    planifest/planifest-framework/planifest-framework/external-skills/requirement-elicitation Skill

    0★ repo

    Requirement elicitation workflow for collecting, reconciling, and structuring evidence before requirement baseline writing. Use when requirement inputs are incomplete and teams need high-confidence evidence gathering; do not use for final canonical requirement synthesis.

  • Requirement prioritization

    planifest/planifest-framework/planifest-framework/external-skills/requirement-prioritization Skill

    0★ repo

    Requirement prioritization workflow for dependency-aware ranking and release cut-line decisions. Use when finalized requirement baselines need ordering under value, risk, and capacity constraints; do not use for requirement discovery.

  • Site architecture

    planifest/planifest-framework/planifest-framework/external-skills/site-architecture Skill

    0★ repo

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.

    The same file is in 4 other repositories

  • Spec driven development

    planifest/planifest-framework/planifest-framework/external-skills/spec-driven-development Skill

    0★ repo

    Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

    The same file is in 1 other repository

  • Stakeholder interview

    planifest/planifest-framework/planifest-framework/external-skills/stakeholder-interview Skill

    0★ repo

    Internal stakeholder interview workflow for capturing constraints, decision authority, and policy requirements. Use when delivery is blocked by unresolved business, engineering, legal, security, or operations decisions; do not use for end-user behavior research.

  • Testing regression strategy

    planifest/planifest-framework/planifest-framework/external-skills/testing-regression-strategy Skill

    0★ repo

    Risk-based regression suite curation for release gating under time and budget limits. Use when teams must decide what runs always versus conditionally by impact and risk; do not use for implementing a single test type in isolation.

  • User story writing

    planifest/planifest-framework/planifest-framework/external-skills/user-story-writing Skill

    0★ repo

    User story authoring workflow for turning prioritized requirements into implementable, testable delivery slices. Use when approved requirement work must be decomposed for sprint execution; do not use for initial requirement discovery or release-level prioritization.

  • Planifest spec agent

    planifest/planifest-framework/planifest-framework/skills/planifest-spec-agent Skill

    0★ repo

    Produces requirements artifacts (execution plan, OpenAPI spec (if applicable), scope, risk register, domain glossary) for a feature. Invoked by the orchestrator during the Requirements step.

  • Prd

    mifunedev/skills/skills/prd Skill

    0★ repo

    Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.