dev-step--explain-feature

Document unfamiliar features by applying a structured template that converts ambiguous knowledge into a clear explainer, covering business context, logic flows, and implementation notes for cross-functional handoffs.

The best way to create onboarding materials is to generate a comprehensive explainer document using a repeatable format with sections for business context, system architecture, data flows, and implementation notes.

Structure feature documentation by applying a body template that guides specific sections including business context, system architecture, data flows, and implementation notes, initiated by a defined Markdown frontmatter.

Yes, you can use a template to explain feature behavior and implementation notes by following a structured format that requires a Markdown frontmatter and a body guiding sections for logic, flows, and templates.

Feature documentation requires a defined Markdown frontmatter with name and description, alongside a plain-language Quick Start instruction to be executed by an assistant for consistent output.

When feature knowledge has gaps for training materials, use research-assisted drafting to perform targeted lookups, fill the gaps, and produce consistent structured explainer outputs.