deepflow 0.1.87 → 0.1.89

package/src/skills/gap-discovery/SKILL.md

@@ -4,9 +4,7 @@ description: Discovers requirement gaps during ideation. Use when user describes
 allowed-tools: [AskUserQuestion, Read]
 ---
 
-# Gap Discovery
-
-Proactively identify missing requirements before implementation.
+# Gap Discovery — Proactive Requirement Gap Identification
 
 ## Gap Categories
 
@@ -19,82 +17,31 @@ Proactively identify missing requirements before implementation.
 | **Success criteria** | "How will you know this works?" |
 | **Anti-goals** | "What should this explicitly NOT do?" |
 
-## Implementation
-
-**Use the `AskUserQuestion` tool** to ask structured questions with predefined options.
-
-### AskUserQuestion Format
+## AskUserQuestion Format
 
 ```json
 {
   "questions": [
     {
-      "question": "What file types should be supported?",
-      "header": "File types",
+      "question": "Clear, specific question ending with ?",
+      "header": "Short label (max 12 chars)",
       "multiSelect": true,
       "options": [
-        {"label": "JPG/PNG only", "description": "Standard image formats"},
-        {"label": "Include WebP", "description": "Modern format with better compression"},
-        {"label": "Include GIF", "description": "Animated images supported"},
-        {"label": "Include video", "description": "MP4, WebM formats"}
+        {"label": "Option 1", "description": "What this means"},
+        {"label": "Option 2", "description": "What this means"}
       ]
     }
   ]
 }
 ```
 
-### Guidelines for AskUserQuestion
-
-- **header**: Max 12 characters (e.g., "File types", "Auth", "Storage")
-- **options**: 2-4 choices per question, each with label + description
-- **multiSelect**: Set `true` when choices aren't mutually exclusive
-- **questions**: Max 4 questions per tool call (tool limit)
-- Users can always select "Other" to provide custom input
-
-### Example Questions by Category
-
-**Scope:**
-```json
-{
-  "question": "Should this feature include admin management?",
-  "header": "Scope",
-  "multiSelect": false,
-  "options": [
-    {"label": "Yes, include admin", "description": "Add admin dashboard for management"},
-    {"label": "No, user-only", "description": "Only end-user functionality"},
-    {"label": "Phase 2", "description": "Add admin features later"}
-  ]
-}
-```
-
-**Constraints:**
-```json
-{
-  "question": "What's the maximum file size for uploads?",
-  "header": "Size limit",
-  "multiSelect": false,
-  "options": [
-    {"label": "5 MB", "description": "Conservative, fast uploads"},
-    {"label": "10 MB (Recommended)", "description": "Balanced for most images"},
-    {"label": "25 MB", "description": "High-res photos supported"},
-    {"label": "50 MB", "description": "Large files, slower uploads"}
-  ]
-}
-```
-
-**Dependencies:**
-```json
-{
-  "question": "What authentication is required?",
-  "header": "Auth",
-  "multiSelect": false,
-  "options": [
-    {"label": "Public access", "description": "No login required"},
-    {"label": "Logged-in users", "description": "Require authentication"},
-    {"label": "Role-based", "description": "Different permissions per role"}
-  ]
-}
-```
+| Constraint | Value |
+|-----------|-------|
+| header | Max 12 characters |
+| options | 2-4 per question, each with label + description |
+| multiSelect | true when choices aren't mutually exclusive |
+| questions | Max 4 per tool call |
+| Other | Users can always select "Other" for custom input |
 
 ## Process
 
@@ -102,26 +49,12 @@ Proactively identify missing requirements before implementation.
 2. Identify categories lacking clarity
 3. Use `AskUserQuestion` with 1-4 targeted questions
 4. Wait for answers
-5. Follow up if answers reveal new gaps (another AskUserQuestion call)
-6. Signal when ready: "Requirements clear. Ready to proceed."
-
-## Question Quality
-
-```
-BAD:  "Any other requirements?"
-GOOD: "Max file size for uploads?" with concrete options
-
-BAD:  "What about errors?"
-GOOD: "If upload fails, retry automatically or show error to user?" with clear choices
-```
+5. Follow up if answers reveal new gaps
+6. Signal: "Requirements clear. Ready to proceed."
 
 ## Rules
 
-- Use `AskUserQuestion` tool for structured input
-- Max 4 questions per tool call (tool limitation)
-- Headers max 12 characters
-- 2-4 options per question with descriptions
-- Use multiSelect when choices can combine
-- Be specific, offer choices with trade-offs explained
-- Don't assume - ask
-- Stop when gaps are covered
+- Be specific — offer concrete choices with trade-offs explained
+- BAD: "Any other requirements?" / GOOD: "Max file size?" with concrete options
+- BAD: "What about errors?" / GOOD: "If upload fails, retry or show error?" with choices
+- Don't assume — ask. Stop when gaps are covered.

package/templates/config-template.yaml

@@ -96,6 +96,16 @@ quality:
   # Timeout in seconds to wait for the dev server to become ready (default: 30)
   browser_timeout: 30
 
+# deepflow-dashboard team mode settings
+# dashboard_url: URL of the shared team server for POST ingestion
+# Leave blank (or omit) to use local-only mode (no data is pushed)
+# Example: http://team-server:3334
+dashboard_url: ""
+
+# Port for `npx deepflow-dashboard serve` (team server mode)
+# Default: 3334  (3333 is reserved for local mode)
+dashboard_port: 3334
+
 # Recommended .gitignore entries
 # Add these entries to your .gitignore to exclude instrumentation artifacts
 gitignore_entries:

package/templates/spec-template.md

@@ -37,7 +37,18 @@
 ---
 
 <!--
-Spec Guidelines:
+Spec Layers (onion model):
+Specs don't need to be complete to be useful. The layer is computed
+from which sections exist — /df:plan gates task generation accordingly.
+
+  L0 (Objective only)                    → spikes only
+  L1 (+ Requirements)                    → targeted spikes
+  L2 (+ Acceptance Criteria)             → implementation tasks
+  L3 (+ Constraints, Out of Scope, Tech) → full impact analysis + optimize
+
+Start at L0. Let spikes deepen the spec. Each layer adds knowledge, not guesswork.
+
+Other guidelines:
 - Keep under 100 lines
 - Requirements must be testable
 - Acceptance criteria must be verifiable