@jaimevalasek/aioson 1.3.0 → 1.5.1

package/template/.aioson/tasks/squad-task-decompose.md

@@ -0,0 +1,66 @@
+# Task: Squad Task Decomposition
+
+> Guia de decomposição de executores em tasks granulares.
+
+## Quando usar
+- Durante `@squad create`, ao avaliar cada executor
+- `@squad extend` quando o usuário pede task decomposition retroativa
+
+## Formato de um task file
+
+Salvar em `.aioson/squads/{squad-slug}/agents/{executor-slug}/tasks/{task-slug}.md`:
+
+```markdown
+# Task: {task-name}
+
+> Order: {1, 2, 3...}
+> Executor: @{executor-slug}
+> Input: {what this task receives}
+> Output: {what this task produces}
+
+## Process
+1. {Step 1 — concrete action}
+2. {Step 2 — concrete action}
+3. {Step 3 — concrete action}
+
+## Output Format
+{Schema or description of expected output}
+
+## Output Example
+{15+ lines of realistic output example}
+
+## Quality Criteria
+1. {Measurable criterion}
+2. {Measurable criterion}
+3. {Measurable criterion}
+
+## Veto Conditions
+1. {Hard block — output CANNOT have this}
+2. {Hard block — output CANNOT have this}
+```
+
+## Árvore de decisão
+
+```
+EXECUTOR
+  ├── Faz UMA coisa bem? (reviewer, validator, formatter)
+  │   └── SEM tasks — o agent file é suficiente
+  │
+  ├── Tem processo multi-step repetível?
+  │   ├── 2 steps → provavelmente sem tasks (mantenha simples)
+  │   ├── 3+ steps com outputs distintos → SIM, decompor em tasks
+  │   └── 3+ steps internos → SEM tasks (steps no agent file)
+  │
+  ├── As tasks serão reutilizadas?
+  │   └── SIM → decompor (reusabilidade)
+  │
+  └── Qualidade é crítica e cada step precisa de seus critérios?
+      └── SIM → decompor (controle granular de qualidade)
+```
+
+## Regras
+- Manter o agent file focado na identidade (missão, foco, restrições)
+- Mover detalhes de processo para task files
+- Cada task deve ser independentemente avaliável
+- Tasks executam sequencialmente — output da task N é input da task N+1
+- Adicionar quality criteria por task, não só por executor

package/template/.aioson/tasks/squad-validate.md

@@ -24,7 +24,7 @@ Verifique que existem:
 - `.aioson/squads/<slug>/agents/agents.md` (obrigatório)
 - `.aioson/squads/<slug>/agents/orquestrador.md` (obrigatório)
 - Para cada executor em manifest.executors: o arquivo referenciado existe
-- Diretórios: `output/<slug>/`, `aios-logs/<slug>/`
+- Diretórios: `output/<slug>/`, `aioson-logs/<slug>/`
 
 ### Camada 3 — Validação semântica (básica nesta fase, aprofundada na Fase 2)
 - Slug do manifesto bate com o nome do diretório

package/template/.claude/commands/aioson/agent/deyvin.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Pair programming partner (alias: pair)"
+---
+
+Read `.aioson/agents/deyvin.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/discovery-design-doc.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Discovery and design doc generation"
+---
+
+Read `.aioson/agents/discovery-design-doc.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/genome.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Domain genome creation and application"
+---
+
+Read `.aioson/agents/genome.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/neo.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — System router: see the full picture, get guided to the right agent"
+---
+
+Read `.aioson/agents/neo.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/product.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Product vision, PRD and feature scoping"
+---
+
+Read `.aioson/agents/product.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/profiler-enricher.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Clone profiler: enrichment phase"
+---
+
+Read `.aioson/agents/profiler-enricher.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/profiler-forge.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Clone profiler: forge and validate"
+---
+
+Read `.aioson/agents/profiler-forge.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/profiler-researcher.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Clone profiler: research phase"
+---
+
+Read `.aioson/agents/profiler-researcher.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/squad.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Squad assembly and management"
+---
+
+Read `.aioson/agents/squad.md` and follow all instructions. $ARGUMENTS

package/template/.claude/commands/aioson/agent/tester.md

@@ -0,0 +1,5 @@
+---
+description: "AIOSON — Systematic test engineering for implemented apps (all sizes)"
+---
+
+Read `.aioson/agents/tester.md` and follow all instructions. $ARGUMENTS

package/template/.gemini/GEMINI.md

@@ -8,3 +8,6 @@
 ## Commands
 Use command files in `.gemini/commands/` that point to the same agents in `.aioson/agents/`.
 - Include `aios-ux-ui` for frontend design specification when UI quality is critical.
+- Include `aios-neo` when you want an overview of the project state and guidance on which agent to use next.
+- Include `aios-deyvin` when you want to continue recent work, inspect what changed, or implement a small slice together.
+- `aios-pair` remains as a compatibility alias.

package/template/.gemini/commands/aios-deyvin.toml

@@ -0,0 +1,6 @@
+name = "aios-deyvin"
+description = "Continuity pair programming"
+instruction_file = ".aioson/agents/deyvin.md"
+requires_context = [
+  ".aioson/context/project.context.md"
+]

package/template/.gemini/commands/aios-neo.toml

@@ -0,0 +1,4 @@
+name = "aios-neo"
+description = "System router — see the full picture, get guided to the right agent"
+instruction_file = ".aioson/agents/neo.md"
+requires_context = []

package/template/.gemini/commands/aios-pair.toml

@@ -0,0 +1,6 @@
+name = "aios-pair"
+description = "Compatibility alias for aios-deyvin"
+instruction_file = ".aioson/agents/deyvin.md"
+requires_context = [
+  ".aioson/context/project.context.md"
+]

package/template/.gemini/commands/aios-tester.toml

@@ -0,0 +1,6 @@
+name = "aios-tester"
+description = "Systematic test engineering for implemented apps"
+instruction_file = ".aioson/agents/tester.md"
+requires_context = [
+  ".aioson/context/project.context.md"
+]

package/template/AGENTS.md

@@ -7,8 +7,7 @@ You operate as AIOSON — an AI development squad with specialized agents.
 2. Check whether `.aioson/context/project.context.md` exists
    - If missing: activate @setup agent immediately
    - If present: read it before any action
-3. Check `.aioson/rules/` — if any `.md` files exist, inform the user:
-   > "Project rules active: {n} rule(s) found in `.aioson/rules/`. Each agent will load applicable rules automatically."
+3. If `.aioson/rules/` contains `.md` files, note silently that project rules are active — each agent will load applicable rules automatically via its "Project rules, docs & design docs" section. Do not alarm if the directory is absent or empty.
 
 ## How to invoke agents
 
@@ -17,7 +16,7 @@ Type `@agent-name` in the prompt. Codex will find the agent file and include its
 The agent activates automatically — begin executing its instructions immediately.
 Do not treat the included file as something to quote, summarize, or display back to the user unless the user explicitly asked to inspect the file itself.
 
-Examples: `@setup`, `@dev`, `@squad`, `@genoma`, `@profiler-researcher`
+Examples: `@setup`, `@deyvin`, `@dev`, `@squad`, `@genome`, `@profiler-researcher`
 
 **Option 2 — Natural language:**
 Describe your intent. The agent system will match and execute.
@@ -28,14 +27,16 @@ Describe your intent. The agent system will match and execute.
 | @discovery-design-doc | "prepare the discovery and design doc", "use the discovery design doc agent" |
 | @analyst | "analyze the requirements", "use the analyst agent" |
 | @architect | "design the architecture", "use the architect agent" |
-| @ux-ui | "design the UI", "use the ux-ui agent" |
+| @ux-ui | "design the UI", "use the UI/UX agent" |
 | @product | "define the product vision", "use the product agent", "start the product wizard" |
+| @deyvin | "continue what we were doing", "use the deyvin agent", "let's fix this together" |
 | @pm | "create the user stories", "use the pm agent" |
 | @dev | "implement the feature", "use the dev agent" |
 | @qa | "write the tests", "use the qa agent" |
+| @neo | "where do I start?", "what should I do next?", "show project status", "guide me", "use the neo agent" |
 | @orchestrator | "coordinate this session", "use the orchestrator agent" |
 | @squad | "assemble a squad", "use the squad agent", "montar squad" |
-| @genoma | "generate a genome", "use the genoma agent", "gerar genoma" |
+| @genome | "generate a genome", "use the genome agent", "gerar genome" |
 | @profiler-researcher | "start the profiler research", "profile this person", "pesquisar DNA mental" |
 | @profiler-enricher | "enrich this profile", "analyze this person's cognition", "consolidar perfil cognitivo" |
 | @profiler-forge | "generate the advisor", "forge the genome 3.0", "gerar advisor da persona" |
@@ -43,6 +44,33 @@ Describe your intent. The agent system will match and execute.
 When an agent file is included via @ or described via natural language, read the corresponding file and execute its instructions immediately from the first step.
 Do not answer with "I will open/read/show the file" unless the user explicitly asked to inspect that file.
 
+## Workflow enforcement
+
+When AIOSON manages the session via `aioson workflow:next`, the CLI controls all routing, state, and event emission. The lifecycle instructions are injected into the agent prompt — follow them exactly.
+
+When running Codex directly (without `aioson workflow:next`), these rules apply:
+
+**Hard constraints — no exceptions:**
+- For implementation requests (code changes, feature build, refactor, bugfix), default to workflow routing and execute via the next workflow stage agent (typically `@dev` after required upstream stages).
+- Exception: if the user explicitly activates `@deyvin` (or the compatibility alias `@pair`), it may work directly only as a continuity / pair-programming agent for existing known context and a small validated slice. If the request is a new project, greenfield build, new feature, broad redesign, vague or contradictory, or mixes product + UX + implementation scope, `@deyvin` must hand off immediately and must not code first.
+- Official workflow agents (`@setup`, `@product`, `@analyst`, `@architect`, `@ux-ui`, `@pm`, `@orchestrator`, `@dev`, `@qa`) must stay inside the workflow. Do not answer requests outside the current agent's scope.
+- Between agent handoffs, your ONLY valid output is: which agent is next and why. Do not continue into that agent's work.
+- If `project.context.md` is inconsistent, stale, or partially invalid, repair it inside the workflow when the correct value is objectively inferable from the active context and artifacts.
+- If a context field is still uncertain, route back to `@setup` inside the workflow instead of offering direct execution as a workaround.
+- Never silently bypass workflow after `@setup` or after collecting requirements.
+
+**Tracked execution in external clients:**
+- Runtime telemetry belongs to the AIOSON gateway, not to ad-hoc shell snippets inside the prompt.
+- Use `aioson workflow:next . --tool=<tool>` for tracked workflow sessions.
+- Use `aioson agent:prompt <agent> . --tool=<tool>` when the client does not support slash commands and you want a tracked direct handoff.
+- Use `aioson live:start . --tool=<tool> --agent=deyvin --no-launch` when you want an explicit tracked continuity session envelope before the external client starts working.
+- Inside an active live session, emit milestones via `aioson runtime:emit . --agent=<agent> --type=<event> --summary="..."` instead of opening a parallel `runtime:session:*` session.
+- Use `aioson runtime:emit . --agent=<agent> --type=plan_checkpoint --plan-step=<step>` when the session is attached to an explicit plan and a step has just been completed.
+- Use `aioson live:handoff . --agent=<agent> --to=<next-agent> --reason="..."` when the active agent must transfer the same live session to another AIOSON agent.
+- Monitor active live sessions with `aioson live:status . --agent=<agent> --watch=2` and close them with `aioson live:close . --agent=<agent> --summary="..."`.
+- Plain natural-language activation in external clients can execute agent instructions, but does not guarantee runtime records in the dashboard.
+- Do not try to synthesize dashboard telemetry by emitting `aioson runtime-log` shell snippets from inside the session.
+
 ## Agent files
 - @setup → `.aioson/agents/setup.md`
 - @discovery-design-doc → `.aioson/agents/discovery-design-doc.md`
@@ -50,12 +78,15 @@ Do not answer with "I will open/read/show the file" unless the user explicitly a
 - @architect → `.aioson/agents/architect.md`
 - @ux-ui → `.aioson/agents/ux-ui.md`
 - @product → `.aioson/agents/product.md`
+- @deyvin → `.aioson/agents/deyvin.md` (`@pair` remains as a compatibility alias)
 - @pm → `.aioson/agents/pm.md`
 - @dev → `.aioson/agents/dev.md`
 - @qa → `.aioson/agents/qa.md`
+- @tester → `.aioson/agents/tester.md`
+- @neo → `.aioson/agents/neo.md`
 - @orchestrator → `.aioson/agents/orchestrator.md`
 - @squad → `.aioson/agents/squad.md`
-- @genoma → `.aioson/agents/genoma.md`
+- @genome → `.aioson/agents/genome.md`
 - @profiler-researcher → `.aioson/agents/profiler-researcher.md`
 - @profiler-enricher → `.aioson/agents/profiler-enricher.md`
 - @profiler-forge → `.aioson/agents/profiler-forge.md`

package/template/CLAUDE.md

@@ -7,25 +7,55 @@ You operate as AIOSON.
 2. Check whether `.aioson/context/project.context.md` exists
    - If missing: run `/setup`
    - If present: read it before any action
-3. Check `.aioson/rules/` — if any `.md` files exist, inform the user:
-   > "Project rules active: {n} rule(s) found in `.aioson/rules/`. Each agent will load applicable rules automatically."
+3. If `.aioson/rules/` contains `.md` files, note silently that project rules are active — each agent will load applicable rules automatically via its "Project rules, docs & design docs" section. Do not alarm if the directory is absent or empty.
 
 ## Agents
 - /setup -> `.aioson/agents/setup.md`
 - /discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
 - /analyst -> `.aioson/agents/analyst.md`
 - /architect -> `.aioson/agents/architect.md`
-- /ux-ui -> `.aioson/agents/ux-ui.md`
+- /ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
 - /product -> `.aioson/agents/product.md`
+- /sheldon -> `.aioson/agents/sheldon.md`
+- /deyvin -> `.aioson/agents/deyvin.md`
+- /pair -> `.aioson/agents/deyvin.md` (compatibility alias)
 - /pm -> `.aioson/agents/pm.md`
 - /dev -> `.aioson/agents/dev.md`
 - /qa -> `.aioson/agents/qa.md`
+- /tester -> `.aioson/agents/tester.md`
+- /neo -> `.aioson/agents/neo.md`
 - /orchestrator -> `.aioson/agents/orchestrator.md`
 - /squad -> `.aioson/agents/squad.md`
-- /genoma -> `.aioson/agents/genoma.md`
+- /orache -> `.aioson/agents/orache.md`
+- /genome -> `.aioson/agents/genome.md`
 - /profiler-researcher -> `.aioson/agents/profiler-researcher.md`
 - /profiler-enricher -> `.aioson/agents/profiler-enricher.md`
 - /profiler-forge -> `.aioson/agents/profiler-forge.md`
 
+## Workflow enforcement
+
+When AIOSON manages the session via `aioson workflow:next`, the CLI controls all routing, state, and event emission. The lifecycle instructions are injected into the agent prompt automatically — follow them exactly.
+
+When running Claude Code directly (without `aioson workflow:next`), these rules apply:
+
+**Hard constraints — no exceptions:**
+- You MUST NEVER implement code, produce UI specs, write PRDs, or answer technical tasks outside an activated agent.
+- If the user explicitly activates `/deyvin` or `/pair`, it may act directly only for continuity on existing known context and a small validated slice. If the request is a new project, greenfield build, new feature, broad redesign, vague or contradictory, or mixes product + UX + implementation scope, `/deyvin` must hand off immediately and must not code first.
+- Between agent handoffs, your ONLY valid output is: which agent is next and why. Do not continue into that agent's work.
+- If the user sends an implementation request before setup is complete: do not implement. Tell them to activate `/setup` first.
+- If the user insists on bypassing an agent stage: refuse and redirect. Urgency or complexity do not override this rule.
+
+**Tracked execution in external clients:**
+- Runtime telemetry belongs to the AIOSON gateway, not to ad-hoc shell snippets inside the prompt.
+- Use `aioson workflow:next . --tool=claude` for tracked workflow sessions.
+- Use `aioson agent:prompt <agent> . --tool=claude` when you want a tracked direct handoff before continuing in Claude Code.
+- Use `aioson live:start . --tool=claude --agent=deyvin --no-launch` when you want an explicit tracked continuity session envelope before Claude Code starts working.
+- Inside an active live session, emit milestones via `aioson runtime:emit . --agent=<agent> --type=<event> --summary="..."` instead of opening a parallel `runtime:session:*` session.
+- Use `aioson runtime:emit . --agent=<agent> --type=plan_checkpoint --plan-step=<step>` when the session is attached to an explicit plan and a step has just been completed.
+- Use `aioson live:handoff . --agent=<agent> --to=<next-agent> --reason="..."` when the active agent must transfer the same live session to another AIOSON agent.
+- Monitor active live sessions with `aioson live:status . --agent=<agent> --watch=2` and close them with `aioson live:close . --agent=<agent> --summary="..."`.
+- Plain slash-command activation registers in the dashboard automatically via `aioson agent:done` at the end of each agent session — each agent file has the call in its "Observability" section.
+- Do not call `aioson runtime-log` directly from inside the session — use `aioson agent:done` instead, which is safe in both direct and live-session contexts.
+
 ## Golden rule
 Small project, small solution.

package/template/OPENCODE.md

@@ -7,15 +7,21 @@
 
 ## Available agents
 - setup -> `.aioson/agents/setup.md`
+- discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
 - analyst -> `.aioson/agents/analyst.md`
 - architect -> `.aioson/agents/architect.md`
-- ux-ui -> `.aioson/agents/ux-ui.md`
+- ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
+- product -> `.aioson/agents/product.md`
+- deyvin -> `.aioson/agents/deyvin.md`
+- pair -> `.aioson/agents/deyvin.md` (compatibility alias)
 - pm -> `.aioson/agents/pm.md`
 - dev -> `.aioson/agents/dev.md`
 - qa -> `.aioson/agents/qa.md`
+- tester -> `.aioson/agents/tester.md`
+- neo -> `.aioson/agents/neo.md`
 - orchestrator -> `.aioson/agents/orchestrator.md`
 - squad -> `.aioson/agents/squad.md`
-- genoma -> `.aioson/agents/genoma.md`
+- genome -> `.aioson/agents/genome.md`
 - profiler-researcher -> `.aioson/agents/profiler-researcher.md`
 - profiler-enricher -> `.aioson/agents/profiler-enricher.md`
 - profiler-forge -> `.aioson/agents/profiler-forge.md`