promptor

name: promptor description: >- Transform voice dictations or raw text into structured development briefs with intelligent multi-task detection. Supports session mode for batch processing, auto-generates implementation plans with subtasks, and exports directly to Notion via MCP. Features 3 complexity levels (quick fix 1h, standard 4h, major 8h). Use when: processing voice memos, dictated specifications, "promptor session", structuring project notes into actionable Notion tasks. Not for: email writing, meeting minutes, executing code, EPCI workflow tasks. allowed-tools: [Read, Glob, Grep, Write, Bash]

Promptor — Dictation to Notion Tasks

Overview

Promptor transforms raw voice dictations or unstructured text into clean, professional development briefs and exports them directly to Notion. Standalone tool, independent from EPCI workflow.

Core Principle: Faithful extraction, never invention. Generate actionable briefs with intelligent subtask suggestions.

Language: Output matches input language. Mixed input defaults to French structure with English technical terms preserved.

Decision Tree

┌─────────────────────────────────────────────────────────────────┐
│                    How is Promptor activated?                    │
└─────────────────────────────────────────────────────────────────┘
                            │
            ┌───────────────┴───────────────┐
            ▼                               ▼
┌───────────────────────┐       ┌───────────────────────┐
│   ONE-SHOT MODE       │       │   SESSION MODE        │
│  /promptor [input]    │       │  /promptor session    │
└───────────┬───────────┘       └───────────┬───────────┘
            │                               │
            ▼                               ▼
    Process one dictation           Init session + project
    Generate brief(s)               → Each input isolated
    Export to Notion                → Multi-task detection
    Done                            → Direct Notion export
                                    → "fin session" to end

Configuration

Notion Configuration

Read from .claude/settings.local.json:

{
  "notion": {
    "token": "ntn_xxx",
    "tasks_database_id": "xxx",
    "default_project_id": "xxx"
  }
}

⚠️ Validation Stricte Projet (MANDATORY)

CRITICAL: Le projet est OBLIGATOIRE pour l'export Notion. Pas de fallback silencieux.

Au démarrage de session ou one-shot :

1. Lire .claude/settings.local.json
2. Vérifier présence des 3 champs notion:
   ├─ token         → ERREUR si absent/vide
   ├─ tasks_database_id → ERREUR si absent/vide
   └─ default_project_id → ERREUR si absent/vide (MANDATORY)
3. Si validation échoue:
   └─ STOP avec message explicite (pas de fallback)

Messages d'erreur :

Comportement :

• ❌ INTERDIT : Export sans projet → tâche orpheline
• ❌ INTERDIT : Fallback silencieux vers affichage texte si projet manquant
• ✅ REQUIS : Bloquer et demander configuration avant export

Validation script :

python src/scripts/validate_notion_config.py

Session Mode

Activation

• /promptor session

Session Workflow

1. INIT: User activates session
   → Read Notion config from settings.local.json
   → Confirm session active

2. DICTATION RECEIVED:
   → Clean voice artifacts
   → Detect mono vs multi-task
   → If multi: show checkpoint for validation
   → Generate brief(s)
   → Export to Notion (if configured)
   → Reset context for next dictation

3. END: "fin session"
   → Show summary with all created tasks

Session Commands

→ See Checkpoint Format

Multi-Task Detection

Mode: AGGRESSIVE

The skill tends toward detecting multiple tasks. User can merge if needed.

Detection Algorithm

1. Clean dictation (keep rupture markers)
2. Segment on explicit/implicit markers
3. Score each segment for independence
4. Decide: ≥2 segments with score ≥40 → MULTI-TASK

Rupture Markers

→ See Multi-Task Detection

Checkpoint Validation

When multi-task detected, show validation checkpoint:

📋 **N tâches détectées**

┌───┬─────────────────────────┬──────────┬────────────┬───────┐
│ # │ Titre suggéré           │ Type     │ Complexité │ Temps │
├───┼─────────────────────────┼──────────┼────────────┼───────┤
│ 1 │ [Title]                 │ [Type]   │ [Level]    │ [Est] │
└───┴─────────────────────────┴──────────┴────────────┴───────┘

📖 Commandes: ok | ok 1,2 | merge 1,2 | edit N "x" | drop N

→ See Checkpoint Format

Complexity Levels

→ See Output Format

Brief Structure

Common Elements (all levels)

# [Action Verb] + [Object] — Notion-ready title

📦 **[Complexity]** | ⏱️ [Time] | 🎯 Confidence: [Level]

## Objectif
[2-4 sentences]

## Description  
[Context and functioning]

## Exigences fonctionnelles
- [FR list]

Standard/Major additions

## Plan d'implémentation

1. **[Phase 1]**
   - [ ] Subtask auto-generated

→ See Subtask Templates

Notion Integration

API Direct (via Bash/curl)

Note: Uses direct Notion API instead of MCP due to serialization bug.

Export to Notion via curl command in Bash tool:

curl -s -X POST 'https://api.notion.com/v1/pages' \
  -H "Authorization: Bearer $NOTION_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Notion-Version: 2022-06-28' \
  -d "$JSON_PAYLOAD"

Configuration read from .claude/settings.local.json:

• notion.token — Bearer token
• notion.tasks_database_id — Target database
• notion.default_project_id — Project relation

Schema Auto-Discovery

IMPORTANT: Before creating pages, fetch and cache the database schema to use correct property types.

1. Check cache: .project-memory/cache/notion-schema.json
2. If missing/stale (>24h): Fetch schema from Notion API
3. Use cached schema to format properties correctly
4. On 400 error: Refresh schema and retry once

This prevents errors like "Type is expected to be multi_select" by dynamically detecting property types instead of hardcoding them.

→ See Schema Cache for implementation details.

Properties Filled

Type Mapping

→ See Type Mapping

Fallback (API Error Only)

Note: Fallback s'applique UNIQUEMENT aux erreurs API, PAS à la config manquante.

Config manquante → STOP (voir Validation Stricte Projet)

Erreur API Notion (après validation config OK) :

1. Display complete brief as text
2. Show message: "⚠️ Erreur API Notion — Brief affiché pour copie manuelle"
3. Afficher le brief complet formaté
4. Log l'erreur pour diagnostic

Critical Rules

1. Never ask questions — Produce brief with available info
2. Never invent requirements — Mark absent if not mentioned
3. Never reference source — Brief is self-contained
4. Each dictation = isolated context — No pollution between inputs
5. Later wins — Last stated version overrides earlier

Knowledge Base

References

• Multi-Task Detection — Detection algorithm
• Output Format — 3 brief templates
• Voice Cleaning — Dictation cleanup
• Subtask Templates — Auto-generation rules
• Processing Rules — Extraction methodology
• Type Mapping — Notion type detection
• Schema Cache — Notion schema auto-discovery

Config

• Notion Config — Database configuration

Templates

• Checkpoint Format — Validation display
• Brief Quick Fix — 1h template
• Brief Standard — 4h template
• Brief Major — 8h template

Limitations

This skill does NOT:

• Ask clarifying questions (produces with available info)
• Execute development tasks (brief generator only)
• Modify existing Notion tasks
• Integrate with EPCI workflow (/brief, /epci)

Version

• Current: v1.0.0 (Claude Code)
• Based on: code-promptor v2.1.0 (web)