delivery

Plugin delivery in colombod/ai-augmentation-systems-openai. Commands read from the repo's manifest — 11 days ago.

Skills (16)

• architecture

  Turn an approved PRD into a technical design grounded in existing code or an explicit greenfield baseline, with decisions, spikes, migration plan and test strategy. Use before story decomposition. Produces .delivery/initiatives/initiative/architecture.md.

• brief

  Frame a feature idea, or assess an existing product, and produce a brief. Use at the very start \u2014 when the idea is still a sentence, or when you need an honest account of what a working product gets wrong today. Produces .delivery/initiatives/initiative/brief.md.

• challenge

  Run an adversarial review panel against any pipeline artifact \u2014 brief, research, personas, PRD, prioritisation, design, architecture, roadmap or stories \u2014 and record ranked findings with tracked status. Use before committing to any artifact. Target stays read-only; findings must be resolve

• design

  Turn a design seed \u2014 a brand, a feeling, a reference, a colour \u2014 into a concrete design system with tokens, component specs, states and accessibility rules that implementation can build against. Use after personas and before architecture. Produces .delivery/initiatives/initiative/design-sy

• personas

  Derive customer and end-user personas grounded in whatever evidence exists, graded by how much evidence there actually is. Use after research and before writing scenarios, so the product is specified against real user segments rather than an imagined average user. Produces .delivery/personas/.

• prd

  Turn a product brief into a full PRD with user scenarios, acceptance criteria and non-functional requirements, then stage it into an MVP and later stages that each let a persona finish a journey. Use once the problem and users are settled and you need a specification precise enough to design against

• product

  Frame a greenfield idea or onboard a brownfield project into one evidence-bound product record. Connect customer promises to planned or observed code, check freshness and feature impact, carry owner choices forward, and prepare retirement proposals and record submitted completed outcomes.

• realign

  Fold what a sprint taught back into the plan \u2014 update invalidated assumptions, recalibrate estimates, re-stage priorities and adjust the roadmap. Use after $delivery:sprint-review. Closes the loop so the next cycle starts from what is now known.

• research

  Research the feature space before specifying anything \u2014 how others solve this, what the domain requires, what users complain about today, and what the existing codebase already constrains. Use after the brief and before personas. Produces .delivery/initiatives/initiative/research.md.

• roadmap

  Build a phased delivery roadmap with sequencing, dependencies, critical path, risks and per-phase cut lists. Use once the PRD and architecture exist and you need to know what lands when and in what order. Produces .delivery/initiatives/initiative/roadmap.md.

• simulate

  Put end-user personas in front of the product before building it, in one of two modes. --interview runs non-leading simulated interviews to surface unmet needs and objections (writes .delivery/interviews/). --journey (the default) walks personas step by step through a journey \u2014 an existing prod

• sprint-review

  Assess acceptance of a completed sprint \u2014 criteria actually met, design system conformance, persona journeys now possible, and what the wave taught. Use after $delivery:sprint. Produces an acceptance verdict and feeds the next planning cycle.

• sprint

  Produce a scoped implementation package for a wave of work \u2014 which stories, in what order, with acceptance criteria, design tokens, test commands and required report-back \u2014 for the team's builders or an external runner. With --runner codex|generic, also convert it into that runner's native

• start

  Initialize a delivery planning workspace and initiative without overwriting existing artifacts. Use to begin a planning effort; this preview does not start a shipping team.

• status

  Read a delivery workspace and report planning progress, unresolved findings and missing evidence. Use to understand the current initiative or next planning step; inventory is not runtime verification.

• stories

  Decompose a roadmap phase into self-contained, implementation-ready story files that carry their full context. Use when a phase is about to start and the work needs to be broken into pickable units. Produces .delivery/stories/.

Similar plugins