Results for “test”

Designing, optimizing, and auditing repository structure: directory design, docs/ layout (PRD, specs, ADR), test/script organization, anti-pattern detection. Use for repo layout or migration planning.

Make any software agent-native with HKUDS CLI-Anything — four routed modes: install ready-made harnesses via CLI-Hub (cli-hub list/search/info/install/launch), give agents the cli-hub-meta-skill for autonomous discovery, generate a new harness from any codebase/repo via the 7-phase /cli-anything pipeline, or iterate with :refine/:test/:validate; 40+ harnesses, 2,461 tests, Click CLIs with REPL + --json.

Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking, producing a concrete one-pager.

Compare AI-generated UI variants in a running local app, then keep the chosen option and remove temporary code.

Design the structure, hierarchy, and navigation model for a product's content and features.

Run Mom Test–style customer-discovery interviews to validate or kill an unbuilt idea — generate a non-leading interview guide, conduct or coach the conversations, and synthesize signal vs compliments. Load when the user asks to do customer discovery, run problem interviews, validate an idea with users, run a Mom Test, design an interview guide, or says "talk to customers", "validate the problem", "interview users", "Mom Test this", "did real users want it", "synthesize my interviews", "I just talked to N people". Sub-skill of `venture-exploration`. Hard-bans "would you use this?", solution-pitching, friend/family-only ICP, and treating compliments as validation. Calls `secure-*` before synthesizing any pasted external transcripts.

Transforms vague ideas into structured, actionable concepts through guided divergent and convergent thinking, producing a markdown one-pager.

Orchestrates polyglot distributed applications using Aspire's AppHost, CLI, and MCP server for local development, testing, and deployment.

Guides implementation of new model architectures in NeMo AutoModel through five phases: discovery, implementation, registration, validation, and testing.

Build evidence and narratives that connect design decisions to measurable user, product, and business outcomes.

Interviews the user one question at a time to stress-test a plan or design, exploring the codebase when possible, until reaching a shared understanding.

Generates comprehensive GitHub project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated issue tracking.

Identify what to measure, test, or track to de-risk a product or AI idea across internal and external risk dimensions.

Create product backlog items in Why-What-Acceptance format — independent, valuable, testable items with strategic context. Use when writing structured backlog items, breaking features into work items, or using the WWA format.

Synthesize the current conversation and codebase context into a Product Requirements Document and publish it to the project's issue tracker.

Automates the entire software development lifecycle from PRD to production with zero human intervention, using multi-agent orchestration and memory systems.

Defines end-to-end user experience behavior and interaction logic, covering flow design, state machines, error recovery, validation, accessibility, and testable acceptance criteria.

Turns a natural-language project specification into a complete, runnable starter repository with real code, tests, and CI configuration for any stack.

Design pricing strategies grounded in value delivery, competitive positioning, and willingness to pay. Recommends pricing models, tiers, and experiments.

Stress-tests a plan against the project's domain model and documented decisions, sharpening terminology and updating DOMAIN.md and ADRs inline as decisions crystallize.

Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived palette and self-contained mermaid diagrams. Use when the user wants to turn a stakeholder summary, executive summary, or business summary into an HTML report, generate an HTML version of a summary doc, or produce a shareable HTML file from a summary markdown. Produces an HTML sibling file only; does not publish anything.

Create a six-frame storyboard that shows a user's journey from problem to solution, using a classic narrative arc to build empathy and align stakeholders.

Stress-test ideas, plans, and decisions using structured critical reasoning across five modes: Socratic questioning, dialectic, pre-mortem, red teaming, and evidence audit.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implementation to /mattpocock:tdd.

Stress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.

Maps, documents, and onboards into an existing codebase by generating seven structured documents covering stack, structure, architecture, conventions, integrations, testing, and concerns.

Evaluate acquisition channels using unit economics, customer quality, and scalability to decide whether to scale, test, or kill a growth channel.

Surveys a codebase as a senior advisor and produces prioritized, self-contained implementation plans for other models or agents to execute, without modifying source code.

Analyze ELF binaries for exploitation vectors using checksec, ROPgadget, and pwntools for buffer overflow and ROP chain development during authorized security testing and CTF challenges.

Select the right Proof of Life (PoL) probe type based on hypothesis, risk, and resources to match validation method to the real learning goal.

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots to keep product decisions grounded in evidence.

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

Runs a structured interview that stress-tests a plan against the project's domain model, sharpens terminology, and updates CONTEXT.md and ADRs inline as decisions are made.

Threat modeling workflow for software systems: scope, data flow diagrams, STRIDE analysis, risk scoring, and turning mitigations into backlog and tests. Use when designing new features, reviewing architecture changes, handling sensitive data, or hardening auth/payment/multi-tenant flows.

Maximize form completion rates for lead capture, contact, demo request, application, survey, quote, and checkout forms by diagnosing friction and applying evidence-based optimizations.