planning

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "planning",
  "version": "0.44.4",
  "userConfig": {
    "surface": {
      "type": "string",
      "title": "Question surface for planning:interview",
      "description": "Where /planning:interview renders its question rounds: terminal (default, inline in the conversation) or page (a local 127.0.0.1 page the session watches, where each question is answered and every save reaches the session). Applies only to /planning:interview. Any other value falls back to terminal.",
      "default": "terminal"
    },
    "use_ask_user_question": {
      "type": "boolean",
      "title": "Use AskUserQuestion for interview rounds",
      "description": "When enabled, the planning skills' question rounds (interview, prd, design, plan) render a round of up to 4 independent questions through the AskUserQuestion tool instead of inline prose. Default: inline prose (dictation-friendly).",
      "default": false
    },
    "use_emoji_question_markers": {
      "type": "boolean",
      "title": "Emoji anchors on interview round questions",
      "description": "When enabled, each interview round question leads with a \u2753 anchor on its Q<N> line and its 'My recommendation:' line leads with \u27a1\ufe0f, inline in the terminal and, on the page surface, on the question title and the Recommendation heading. Purely presentational. Q<N> numbering stays the functional handle, and persisted artifacts (ledger, register, Brief) never carry the emoji. Default: plain text. A user instruction against emoji wins over this option, and the page is then started with --emoji-markers false so it matches the terminal.",
      "default": false
    }
  },
  "description": "Pre-implementation planning pipeline: chart a too-big, foggy effort as a decision map, diverge on candidate approaches, lock product intent and the engineering contract, route resolved domain language to the domain-driven-design glossary steward, e