Loading...
Loading...
Found 8 Skills
Bridges design and engineering by producing detailed specs, organized handoff packages, asset inventories, and cross-functional documentation. Part of the Intent design strategy system. Trigger when: writing design specs, preparing engineering handoffs, documenting for development, creating design reviews, writing test plans, building copy matrices, addressing edge cases, aligning stakeholders, packaging designs "for engineering," or saying "write the spec," "prepare the handoff," "document this," or "what do we need for design review?"
Write a clear, decision-ready PRD (and optionally a PR/FAQ, AI eval spec, and prompt set) for cross-functional alignment.
Framework for packaging competitive updates into executive-ready narratives and action plans.
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 Your dev team is building features no one wants, while user-reported bugs have been piling up for three months without being addressed. Operations thinks R&D ignores users; R&D thinks Operations doesn't understand technical constraints. This SOP provides you with a complete Product × Engineering × Operations collaboration framework, from unified Kanban to 10-day iteration cadence to veto power rules. 🇯🇵 Your dev team is building features no one asks for, and user-reported bugs have been left unattended for months. This SOP provides a complete collaboration framework for Product × Engineering × Operations, from unified backlog to 10-day sprints to release veto power. 🇰🇷 Your dev team is building features no one requests, and user-reported bugs have been neglected for months. This SOP provides a complete collaboration framework for Product × Engineering × Operations, from unified backlog to 10-day sprints to release veto power. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "product-engineering-ops-alignment" | "iteration-management" | "product-development-operations" | "product-development-operations" | "product-development-operations"
Structured approach for investigating funnel issues across e-commerce experiences.
Create a comprehensive customer journey map that visualizes how customers interact with your brand across all stages—from awareness to loyalty—documenting their actions, touchpoints, emotions, KPI
Help users define a compelling, qualitative description of a future state that aligns decentralized teams and motivates long-term innovation.
Master stakeholder management, executive communication, cross-functional alignment, and product advocacy. Lead effectively across your organization.