Plugins

3 plugins

Results for “bloc”

12 skills
More results
ahang1598
doubao-product-analysis
围绕具体产品、产品想法或存量方案,产出用于产品进入、定位、竞争策略、上市路径、能力建设与路线图决策的证据型分析报告。适用于“值不值得做或发布”“进入哪个细分”“目标用户和市场是否成立”“竞品为何这样设计”“该借鉴、差异化或放弃什么”“核心能力与 Roadmap 怎么定”“如何调整已有产品”等请求,也适用于将用户研究、市场信息、竞品实测、内部资料和业务约束整合为决策建议。支持 0→1、存量产品调整、竞品专项与组合分析;默认交付为可独立阅读的飞书云文档,并用正文内 HTML5 block 呈现必要的产品定位图或能力路线图。不用于只需罗列功能、直接撰写实施 PRD,或在缺少依据时给出确定性预测的任务。
9 · bundle
akillness
task-planning
Turns vague features, bug clusters, roadmap items, or launch work into an execution-ready planning packet by choosing the right packet type, separating discovery from delivery, and making blockers, dependencies, and the next move explicit.
42 · bundle
deanpeters
problem-statement
Write a user-centered problem statement that captures who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.
5.6k · bundle
peteedoo
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.
0
lionelndong
topic-discovery
Layer 0 of the keyword research pipeline. Builds a topic-graph snapshot for the brand's category before any seed work, approximated from Semrush phrase_related + phrase_questions on the category seeds plus the brand's own ranking footprint (domain_organic_unique). Idempotent on brand-config hash; never blocks the pipeline; cheap.
0
baofeng-tech
notion-workspace
Manage Notion workspace: search pages and databases, read markdown, create pages, insert rows, triggers, MCP. Powered by AISA gateway (Notion toolkit). Requires AISA_API_KEY and curl. Keywords: notion, workspace, page, database, block, markdown, wiki, task board, insert row, OAuth. Use when: the user needs web search, research, source discovery, or content extraction.
1 · bundle
metinduraktr-44
devil
Reviews a product document (PRD, spec, design brief) BEFORE implementation to surface holes — undefined edge cases, missing states, policy gaps — by attacking what the document is SILENT about (things unwritten, and things written only for the happy path). Acts as a strict "sign-off manager," ruling Approve / Conditional / Reject and producing a polite, forwardable question list. Works for planners/PMs (self-review before sharing), engineers (blocking questions before coding), and designers (screen states with no mockup). Use whenever the user wants a spec/PRD/plan/brief checked for readiness or gaps, or says "review this spec", "find holes in this PRD", "poke holes in this", "is this plan good to build?", "can I start implementing this?", "what states/edge cases am I missing?", "what should I ask the PM before coding?", "run devil", or pastes/links a planning document and asks whether it's ready to act on. Do NOT use it to: write or draft a new spec, summarize or translate a document, estimate/break down tic
0 · bundle