nexandro

Mine architecture decision records (ADRs), gotcha files, runbooks, and docs/archive for cross-project lessons that warrant ai-playbook canonical specs. Use when a project lacks a populated retros/ directory but has equivalent material in other forms.

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Orchestrate the canonical task↔PR↔release flow end-to-end. Two modes — `/dev-flow start <description>` scaffolds an OpenSpec change + branch + (optional) worktree + git hook ready for commits; `/dev-flow ship` validates the current branch + pushes + opens PR + monitors CI. Use whenever you start any non-trivial change in a playbook-consuming project. LLM-agnostic — works for Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and humans.

Implement an OpenSpec change in parallel using multiple subagents (one per disjoint task group inside the same slice). Use when the slice's tasks.md has ≥2 task groups with disjoint write-paths AND >30 min of parallelisable work. For sequential implementation use openspec-apply-change instead.

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

Create architecture solution design decisions for AI agent consistency. Use when the user says "lets create architecture" or "create technical architecture" or "create a solution design"

Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

Lossless LLM-optimized compression of source documents. Use when the user requests to 'distill documents' or 'create a distillate'.

Use when the user wants to check the ELIGIA stack for outdated components (Docker, Python, git repos, npm) and apply safe updates with healthcheck rollback.

Use when the user wants to start, resume, or advance a GTM offering through the 38-step development pipeline (Exploration → Formulation → Execution).

Use when the user wants to draft or refresh an offering's enablement plans (Pre-Sale, Sales, Ops) plus the Battlecard and One-Pager.

Use when the user wants a Conventional Commits message drafted (or rewritten) for staged changes, including type/scope/breaking-change footers.

Use when the user wants to draft an Ideation Deck for an offering's internal board pitch — the Step 10 deliverable that gates entry into Formulation.

Use when the user wants to design or update an offering's MONETIZATION_MODEL.md (pricing, rate cards, CPQ, billing, channel/partner economics, contracts).

Úsalo cuando el usuario quiere registrar un nuevo lote de producción de pastelitos y obtener su ficha de costes y QA.

Use when the user wants all local changes staged, committed with an auto-generated message, and pushed to remote in one step.

Use after creating or updating an offering's SALES_ENABLEMENT.md, PRE_SALE_ENABLEMENT.md, or OPS_ENABLEMENT.md to validate BU alignment, TCO completeness, and capability mapping.

Use after generating or editing a PPTX (or invoked by /bc-to-pptx) to visually inspect slides for overlaps, empty areas, data mismatches, and style issues.

Use when the user wants to draft or finalise an offering's Solution Design (SoD), Service Design (SD), Operational Playbook (OP), or Offer Description (OD).

Úsalo cuando el usuario quiere arrancar el stack palafito-prod (Paperclip) y, si hace falta, levantar Docker Desktop antes.

Generates a branded PPTX deck from LEAN_BUSINESS_CASE.md using the Marlink template. Pipeline: Extract BC data -> validate -> inject into template -> QA swarm. Use after LEAN_BUSINESS_CASE.md is approved and ready for presentation. Also use when user says "generate deck", "create slides", "make pptx", "presentation".

Designs portfolio entries following the Unified Catalogue framework (3-Table Model, Delivery Types, SKU Taxonomy). Use when designing products, services, or solutions for an offering.

Develops COMMERCIAL_PLAYBOOK.md: pricing architecture, rate cards, CPQ config, billing ops, partner economics, licence lifecycle, Finance & IT readiness. Use when creating or updating commercial playbooks for offerings. Also use when discussing pricing operations, CPQ configuration, billing setup, or channel economics.

Fetch up-to-date library documentation via Context7 MCP. Given a library name and optional topic, resolves the library ID and retrieves current docs to ground coding tasks in accurate, versioned APIs. Use when implementing features with libraries that change frequently (frameworks, AI SDKs, ORMs, cloud SDKs, etc.).

Produces CPQ_CALCULATOR.xlsx spec: pricing calculator tool derived from COMMERCIAL_PLAYBOOK.md rate card + BC §4.5. Use when creating CPQ pricing calculators, quote tools, or pricing spreadsheets for offerings.

Provides segment and persona expertise with customer journey mapping. Use when analyzing target segments, personas, or customer needs for offerings.

Produces DATASHEET.md: customer-facing technical sheet derived from OD + SolD. Use when creating or updating datasheets for offerings. Also use when the user needs a customer-facing technical summary or product sheet.

Extract clean markdown from web pages using the Defuddle CLI — removes navigation, ads, and clutter to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze (articles, docs, blog posts). Do NOT use for URLs ending in .md (already markdown — use WebFetch directly). Requires: npm install -g defuddle

Guides users through structured workflow for co-authoring documentation, proposals, technical specs.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images, performing find-and-replace, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill.

Loads strategic and market intelligence context silently. Use this skill whenever working on offerings, business strategy, market analysis, competitive positioning, customer segments, personas, or value propositions. Also use when the user mentions ABC Goals, CIT OKRs, Marlink strategy, target segments, or any offering in 20_OFFERS/.

Create and edit Obsidian JSON Canvas (.canvas) files — visual node/edge graphs for spatial note organization. Use when working with .canvas files or when the user asks to create a visual map, diagram, or canvas in Obsidian.

Web research agent that populates 00_Research/ files (market.md, financial.md, competitive.md, customer.md, technical.md) for offerings. Run FIRST when starting a new offering, after /develop creates the folder structure. Calls /qa-research for validation.

Processes global market research inputs and updates master indices (segments, personas, competitive, industries). Run when new reports are added to 10_MARLINK/40_Market/input/.

Guide for creating MCP (Model Context Protocol) servers in Python (FastMCP) or Node/TypeScript.

Create and edit Obsidian Bases (.base files) — database-like views of notes with filters, formulas, and summaries. Use when working with .base files, creating table/card/list/map views of vault notes, or when the user mentions Bases, database views, filters, or formulas in Obsidian.

Interact with Obsidian vaults using the Obsidian CLI — read, create, search, and manage notes, tasks, properties, and more. Also supports plugin development (reload, eval, DOM inspection). Use when the user asks to interact with an Obsidian vault from the command line. Requires: npm install -g @obsidianmd/obsidian-cli