Results for “plan-structure”

Install a local rebuttal workspace for academic papers with structured intake, reviewer analysis, and strategy planning to produce venue-compliant author responses.

Create structured memoranda of understanding for partnerships, including context, key components, action plans, and success metrics.

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.

Builds a feature specification from scratch through a relentless, evidence-based interview that walks the design tree decision-by-decision, resolving dependencies as it goes. Use when the user wants to plan, design, scope, specify, or flesh out a new feature, capability, or system behavior before implementation. Produces a feature specification focused on system behaviors, not implementation detail. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features — use project-documentation. Does not design the contract for an interface — use design-an-api. Does not research open-ended options before there is a feature to specify — use research.

Develops milestone-based project descriptions for Research, Prototype, and follow-on production Other Transactions, including objectives, phases, go/no-go structures, transition planning, and cost-analysis handoffs.

Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.

Build visually engaging scientific slide decks for conferences, seminars, defenses, and research talks with structured planning, design templates, and automated image generation.

Structures a Request for Comments (RFC) document for proposing significant technical changes that require cross-team input and approval, guiding authors through problem definition, proposed solution, alternatives analysis, and rollout planning.

Collaboratively write multi-volume novels with structured commands for outlining, planning, drafting, writing, health-checking, and archiving, while maintaining world-building consistency across chapters.

Execute QA test plans on Holoscan Sensor Bridge hardware by reading a test document, filtering tests by setup, running automatable tests with pass/fail evaluation, and producing a structured report.

Use this skill whenever a user wants to create a presentation outline, slide deck structure, storyboard slides, or plan a deck for any context (talk, boardroom, email report). Also use when the user mentions "help me structure my presentation", "slide outline", "storyboard my deck", "presentation flow", "plan my slides", "key message for my deck", "pyramid principle for slides", "what slides should I include", or "help me tell a story with slides". This skill walks through a complete, interactive process in two phases: Phase 1 (setup → key message → storyboard) saves a slide-outline.md; Phase 2 (interactive per-slide copy drafting → polish) saves a slide-copy.md that is linked from slide-outline.md. Trigger even when the user only mentions a vague intent like "I need to present X to my team" or "help me put together a board deck".

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for writing documentation or architectural decision records.