Feature Doc Splitter

Overview

Use this skill to turn an early feature note into a small documentation set that engineers can implement independently. The output is three build-ready documents: an overview document, a frontend implementation document, and a backend implementation document.

The documentation must connect the request to the real codebase, separate frontend and backend responsibilities, define shared contracts, include required Mermaid diagrams, and make unknowns explicit. For new UI surfaces, the workflow also decides whether optional Pencil placeholders should be reserved.

When to Use

Use this skill when the user asks to:

• Split an initial feature requirement document into overview, frontend, and backend implementation documents.
• Convert rough product notes into build-ready technical documentation.
• Inspect an existing codebase before writing feature implementation docs.
• Add Mermaid business flows, interaction flows, sequence diagrams, or API contract indexes.
• Ask whether new frontend UI surfaces should reserve optional Pencil design placeholders.

Do not use