sales-marketing
1
phase-02-requirements-scope
Define detailed functional, non-functional, security, compliance, and data requirements. Create requirements traceability matrix and get stakeholder sign-off.
Harery
business
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
sales-marketing
1
userstory-documentation
User story, epic, and task creation with acceptance criteria. Use when breaking down requirements into user stories, creating epics, writing acceptance criteria, or planning sprints. Triggers on "user story", "epic", "acceptance criteria", "sprint planning", "story points".
foolpoet44
business
sales-marketing
1
brainstorm-proof-of-concept-plan
Use when requirements specify risky technical assumptions, unfamiliar APIs, or complex integrations before implementing full features - creates sequential POC plans with parallel research validation, design documentation, and risk mitigation for incremental confidence building
WesleyMFrederick
business
sales-marketing
1
invest-stories
When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.
CoderMariusz
business
sales-marketing
1
feature-development-workflow
Orchestrate end-to-end feature development from requirements through implementation, testing, and review. Use when: (1) planning feature development stages, (2) coordinating multi-agent feature workflows, (3) understanding SDLC phases for new features.
thapaliyabikendra
business
sales-marketing
1
systematic-planning
Systematic feature planning workflow - use when starting complex features requiring structured approach
ashchupliak
business
sales-marketing
1
brainstorming
Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation through collaborative dialogue.
rbergman
business
sales-marketing
1
sprint-plan
Create comprehensive sprint plans by intelligently grouping estimated user stories based on velocity, dependencies, priorities, and risk. This skill should be used during sprint planning ceremonies to transform backlog into actionable sprint commitments.
adolfoaranaes12
business
sales-marketing
1
event-management
Planning and executing developer events, conferences, and meetups
pluginagentmarketplace
business
sales-marketing
1
kano-agent-backlog-skill
Local-first, multi-product backlog management with agent collaboration discipline.
dorgonman
business
sales-marketing
1
code-planning
Plan implementation changes before coding. Use when the user requests a new feature, modification, or asks for a plan. Ensures full understanding, discovers existing code, creates detailed file/folder structure with contracts and tests, and gets user approval before implementation.
StupidIncarnate
business
sales-marketing
1
kano-agent-backlog-skill
Local-first, multi-product backlog management with agent collaboration discipline.
dorgonman
business
sales-marketing
1
ue
UE (user experience engineering) skill for defining end-to-end user experience behavior and interaction logic. Use for tasks like flow design, interaction models, state machines, error recovery, input validation, usability heuristics, accessibility, and turning UX intent into testable acceptance criteria for implementation.
muzhicaomingwang
business
sales-marketing
1
feedback-collector
Systematically gather, organize, and act on user feedback
violetio
business
sales-marketing
1
project-mngt
Product Owner / Project Manager skill for MVP/MMP/MMR implementation planning
vladm3105
business
sales-marketing
1
spec-context-loader
spec（仕様書）が存在する場合の文脈収集を担当するSkill。requirements.md、design.md、qa-tests/から要件・設計・テスト仕様を抽出し、構造化して返却します
einja-inc
business
sales-marketing
1
spec-flow-analyzer
Use this agent when you have a specification, plan, feature description, or technical document that needs user flow analysis and gap identification. This agent should be used proactively when:\n\n<example>\nContext: The user has just finished drafting a specification for OAuth implementation.\nuser: "Here's the OAuth spec for our new integration:\n[OAuth spec details]"\nassistant: "Let me use the spec-flow-analyzer agent to analyze this OAuth specification for user flows and missing elements."\n<commentary>\nSince the user has provided a specification document, use the Task tool to launch the spec-flow-analyzer agent to identify all user flows, edge cases, and missing clarifications.\n</commentary>\n</example>\n\n<example>\nContext: The user is planning a new social sharing feature.\nuser: "I'm thinking we should add social sharing to posts. Users can share to Twitter, Facebook, and LinkedIn."\nassistant: "This sounds like a feature specification that would benefit from flow analysis. Let me use the spec-flow
i3ringit
business
sales-marketing
1
brainstorming
Transform rough ideas into solid designs through structured questioning
a-ariff
business
sales-marketing
1
spec
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, migrations, performance, documentation, or any other work type. Triggers: spec, requirements, define scope, what to build.
doodledood
business
sales-marketing
1
first-principles-pm
First-principles project management - from idea to execution with maximum efficiency. Use when starting projects, evaluating requirements, or managing development workflow.
Petrus-Han
business
sales-marketing
1
feature-planning
Plan new features end-to-end with PRD and parallelized tasks. Use when user describes a new feature, says "I want to build", "let's add", "implement", or asks for requirements, specs, or task breakdown.
haulmatic-dev
business
sales-marketing
1
product-owner
Product Owner responsible for Vision, Scope, and Backlog management. Validates features against business goals. Use this skill for vision creation, scope definition, or feature validation.
Denissvgn
business
sales-marketing
1
requirements-engineering
Translating user prompts into structured requirements, user stories, and beads tasks for systematic implementation. Trigger keywords: requirements, user story, acceptance criteria, as a, i want, so that, given when then, task breakdown, epic creation
Kaakati
business