Results for “engineering-planning”

10 skills

Analyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.

More results

brycewang-stanford

Use when planning an ASE (IEEE/ACM Automated Software Engineering) research-track campaign backward from the deadline, through abstract registration, the double-anonymous submission, the early-rejection gate, rebuttal, the criteria-bound revision round, artifact evaluation, and the camera-ready in both IEEE Xplore and the ACM Digital Library.

site-architecture

Audit, redesign, or plan website structure, URL hierarchy, navigation, and internal linking to improve SEO and user experience.

20.4k · bundle

Creates a strategic SEO plan for new or existing websites, covering competitive analysis, site architecture, content strategy, technical foundation, and a phased implementation roadmap.

nimoqup046-collab

Builds a strategic SEO plan for new or existing websites, covering competitive analysis, site architecture, content strategy, technical foundation, and a phased implementation roadmap.

site-architecture

Plan website page hierarchy, navigation, URL patterns, and internal linking for improved SEO and user experience.

36.3k · bundle

Generate a comprehensive SEO strategy and implementation roadmap for new or existing websites, including competitive analysis, content planning, and technical foundation.

42.4k · bundle

site-architecture

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.

growth-strategy

Growth strategy for product-led and loop-driven growth systems. Use when building growth strategy, designing growth loops, planning acquisition channels, evaluating network effects, deciding when to scale, or coordinating product, engineering, data, and marketing around growth. For SEO audits use seo-and-aeo-strategy; for page/form CRO use conversion-rate-optimization; for A/B test design use ab-test-setup.