common-engineering

Use this agent PROACTIVELY when fetching official library documentation, API references, or code examples. MUST BE USED for tech libraries/frameworks, official docs, API references, or library suggestions for development tasks. Use web-research-specialist for debugging or community solutions.

Mermaid diagram specialist. Proactively creates and validates sequence, architecture, or flowchart diagrams using common-engineering:mermaid. Use when users request Mermaid or diagrams. MUST BE USED for diagram requests.

Technical documentation specialist for creating one-pagers, RFCs, TSDs, ADRs, POC/Experiment documents, and other engineering design documents. Routes directly to the appropriate focused skill based on document type. Guides users interactively through context gathering and generates polished documents. Proactively trigger when users mention writing docs, proposals, specs, design documents, or technical documentation.

Use this agent PROACTIVELY when users need comprehensive web research across any topic. MUST BE USED for debugging help, news/current events, business research, general web queries, or community solutions. Use librarian agent for official library documentation instead.

This skill should be used when the user asks to "write an ADR", "create an ADR", "document an architecture decision", "write an Architecture Decision Record", "document a technology choice", "compare database options", "document why we chose X over Y", or needs to record a specific architectural or technology decision with alternatives and trade-offs (1-3 pages). Use when capturing a decision that needs to be justified and preserved for future reference.

Create validated Mermaid diagrams (sequence, architecture, flowchart) with automatic syntax checking and self-healing. Use when users request diagrams, visualizations of API flows, system architecture, or process documentation. All diagrams are validated with mermaid-cli before delivery.

This skill should be used when the user asks to "write a one-pager", "create a one-pager proposal", "draft a one-pager", "write a proposal doc", "create a feature proposal", "write a proposal for sign-off", or needs a concise stakeholder approval document (1-3 pages). Produces focused proposal documents with problem statement, goal, proposed solution, alternatives, and risks.

This skill should be used when the user asks to "write a POC document", "document a proof of concept", "write a POC report", "document an experiment", "write an experiment report", "document technical evaluation results", "write a Go/No-Go recommendation", "capture POC findings", or needs to document hypothesis validation, technology evaluation, or feasibility study results with a clear Go/No-Go decision (3-8 pages).

Generate project management plan Excel workbooks (.xlsx) with automated Gantt charts, team charters, budget tracking, and RAID logs. Use when users request a "project management plan", "PM plan", "program plan", "project tracker", "project plan excel", "project plan spreadsheet", or need to create a structured project planning workbook. Follows an interactive 3-phase workflow: brainstorm with the user, get plan approval, then generate the workbook.

This skill should be used when the user asks to "write an RFC", "create an RFC", "draft an RFC", "write a Request for Comments", "write a design proposal for cross-team review", "document a complex architecture change", or needs a detailed design document covering architecture, implementation phases, migration, and rollback planning (5-15 pages). Use for complex multi-service changes requiring thorough cross-team review.

This skill should be used when the user asks to "write a TSD", "create a TSD", "write a Technical Specification Document", "document an API", "spec out an API", "write an API spec", "document a data model", "write a technical spec", "create interface documentation", or needs a comprehensive technical specification covering API endpoints, data models, interface contracts, error handling, and versioning (5-20 pages).