qualia-framework 5.5.0 → 5.9.0

package/skills/qualia-task/SKILL.md

@@ -1,98 +0,0 @@
----
-name: qualia-task
-description: "Single focused task with a FRESH builder subagent spawn — 1-3 hours, 1-5 files, atomic commit, validation contract. Heavier than /qualia-quick (which runs inline with no spawn) but lighter than /qualia-build (which needs a phase plan). Use when the user says 'build this one thing', 'add a component', 'implement this feature', 'qualia-task', or for any 1-5 file feature outside a full phase."
-allowed-tools:
-  - Bash
-  - Read
-  - Write
-  - Edit
-  - Agent
-  - AskUserQuestion
----
-
-# /qualia-task — Single Task Builder
-
-Build one thing properly. Fresh builder context, atomic commit, but no phase plan needed.
-
-## Usage
-`/qualia-task` — describe what to build interactively
-`/qualia-task {description}` — build it directly
-
-## When to Use
-- One feature, 1-5 files, clear scope, 1-3 hours of work
-- Adding a single feature, component, API route, or integration
-- Refactoring one module
-- Building something specific someone asked for
-
-## Process
-
-### 1. Clarify
-
-If no description provided, ask: **"What do you want to build?"**
-
-Then use AskUserQuestion:
-
-```
-question: "How complex is this task?"
-header: "Scope"
-options:
-  - label: "Small (1-2hrs)"
-    description: "Single file or component, straightforward implementation"
-  - label: "Medium (2-3hrs)"
-    description: "Multiple files, some integration work, needs testing"
-  - label: "Large (3hrs+)"
-    description: "Significant feature, multiple components — use /qualia-plan instead"
-```
-
-If "Large" — suggest `/qualia-plan` instead. Ask if they want to proceed anyway.
-
-### 2. Task Spec
-
-Write a quick task spec (don't save to file, just confirm with user):
-
-```bash
-node ~/.claude/bin/qualia-ui.js banner task
-node ~/.claude/bin/qualia-ui.js info "What: {what to build}"
-node ~/.claude/bin/qualia-ui.js info "Files: {files to create/modify}"
-node ~/.claude/bin/qualia-ui.js info "Done: {what done looks like}"
-```
-
-Ask: **"Good to build?"**
-
-### 3. Build
-
-Spawn a builder agent with the task:
-
-```
-Agent(subagent_type: "qualia-builder")
-
-Task: {task description}
-Files: {files to create/modify}
-Acceptance Criteria: {observable completion criteria, 1-3 bullet points}
-
-Context: Read PROJECT.md if it exists. Follow all rules (security, frontend, deployment).
-```
-
-The builder runs in fresh context — reads before writing, follows rules, commits atomically.
-
-### 4. Verify
-
-After the builder finishes:
-- Run `npx tsc --noEmit` if TypeScript
-- Quick smoke test if applicable
-- Review what was built
-
-### 5. Report
-
-```bash
-node ~/.claude/bin/qualia-ui.js divider
-node ~/.claude/bin/qualia-ui.js ok "Task: {description}"
-node ~/.claude/bin/qualia-ui.js ok "Files: {files changed}"
-node ~/.claude/bin/qualia-ui.js ok "Commit: {commit hash}"
-node ~/.claude/bin/qualia-ui.js end "TASK COMPLETE"
-```
-
-```bash
-node ~/.claude/bin/state.js transition --to note --notes "{task description}" --tasks-done 1
-```
-Do NOT manually edit STATE.md or tracking.json — state.js handles both.