What problem does it solve? Starting a new feature or initiative often produces inconsistent, incomplete planning documents that skip risks, NFRs, and acceptance criteria, leading to misaligned teams and rework later. This Skill structures the creation of AI-DLC Feature (Intent) documentation with iterative human-in-the-loop review, explicit publish gates, and traceability to source requirement documents. ## Core Features & Use Cases - Multi-backend Feature docs: Draft and publish Feature documentation to GitLab (markdown with MR review), Linear (native Initiatives), or Confluence (pages with Jira integration). - Gear-based scaling: Choose Quick, Standard, or Deep ceremony levels so the documentation depth matches the size and risk of the work. - Source-derived Intents: Ingest an existing BRD/PRD, record its version, and build a traceability matrix, validation record, and MVP slice proposal. - Publish gate and index: Enforce explicit user approval before creating any artifact, then register the Feature in a central Features Index. - Use Case: A product manager asks to create a Feature doc for a new authentication system; the Skill gathers context, drafts the brief, gets explicit publish approval, creates a GitLab MR, and hands off to the elaboration phase. ## Quick Start Ask the assistant to create a Feature document for your new initiative, for example by saying: create an intent for adding user authentication with OAuth2 support.
