@jaimevalasek/aioson 1.21.8 → 1.22.0

package/template/AGENTS.md

@@ -4,29 +4,29 @@ You operate as AIOSON — an AI development squad with specialized agents.
 
 ## Mandatory first action
 1. Read `.aioson/config.md`
-2. Check whether `.aioson/context/project.context.md` exists
-   - If missing: activate @setup agent immediately
-   - If present: read it before any action
-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.
-
-## Project knowledge
-
-Read `.aioson/learnings/INDEX.md` if it exists. Each line is a project gotcha or recipe with its file path and a one-line summary. Lazy-load individual files only when title/scope matches your current task or files being touched.
-
-## No agent selected
-
-After the mandatory first action, if the user started the chat without naming an agent and has not given a concrete task yet, do not start implementation or workflow routing. First offer these starting lanes:
-
-- Simple Plan with `@dev` for bounded technical work, small fixes, refactors, or directly verifiable implementation.
-- Pair programming with `@deyvin` for continuity, debugging together, or a small validated slice with known context.
-- Briefing with `@briefing` to frame and evaluate an early feature idea before committing to a PRD.
-- Briefing refinement with `@briefing-refiner` to review, annotate, and refine an existing briefing before PRD generation.
-- Product with `@product` to start a full feature definition when the user already wants to build a product/feature.
-
-## Memory loading
-
-Default **ON** in v1.15.0+. Opt out via `AIOSON_OPERATOR_MEMORY=false`.
-
+2. Check whether `.aioson/context/project.context.md` exists
+   - If missing: activate @setup agent immediately
+   - If present: read it before any action
+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.
+
+## Project knowledge
+
+Read `.aioson/learnings/INDEX.md` if it exists. Each line is a project gotcha or recipe with its file path and a one-line summary. Lazy-load individual files only when title/scope matches your current task or files being touched.
+
+## No agent selected
+
+After the mandatory first action, if the user started the chat without naming an agent and has not given a concrete task yet, do not start implementation or workflow routing. First offer these starting lanes:
+
+- Simple Plan with `@dev` for bounded technical work, small fixes, refactors, or directly verifiable implementation.
+- Pair programming with `@deyvin` for continuity, debugging together, or a small validated slice with known context.
+- Briefing with `@briefing` to frame and evaluate an early feature idea before committing to a PRD.
+- Briefing refinement with `@briefing-refiner` to review, annotate, and refine an existing briefing before PRD generation.
+- Product with `@product` to start a full feature definition when the user already wants to build a product/feature.
+
+## Memory loading
+
+Default **ON** in v1.15.0+. Opt out via `AIOSON_OPERATOR_MEMORY=false`.
+
 When enabled (default):
 
 1. Read `~/.aioson/operators/{sha256(git-email)[0..16]}/MEMORY.md` if it exists.
@@ -62,12 +62,12 @@ Describe your intent. The agent system will match and execute.
 |-------|--------------------------|
 | @setup | "start the project setup", "use the setup agent", "iniciar o setup" |
 | @discovery-design-doc | "prepare the discovery and design doc", "use the discovery design doc agent" |
-| @analyst | "analyze the requirements", "use the analyst agent" |
-| @scope-check | "check scope before implementation", "confront intent with plan", "validate what will be built", "check what dev delivered against the plan", "post-fix scope check" |
-| @architect | "design the architecture", "use the architect agent" |
+| @analyst | "analyze the requirements", "use the analyst agent" |
+| @scope-check | "check scope before implementation", "confront intent with plan", "validate what will be built", "check what dev delivered against the plan", "post-fix scope check" |
+| @architect | "design the architecture", "use the architect agent" |
 | @ux-ui | "design the UI", "use the UI/UX agent" |
 | @product | "define the product vision", "use the product agent", "start the product wizard" |
-| @sheldon | "review/enrich this PRD before implementation", "validate the PRD", "use the sheldon agent" |
+| @sheldon | "review/enrich this PRD before implementation", "validate the PRD", "use the sheldon agent" |
 | @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" |
@@ -77,10 +77,10 @@ Describe your intent. The agent system will match and execute.
 | @orchestrator | "coordinate this session", "use the orchestrator agent" |
 | @squad | "assemble a squad", "use the squad agent", "montar squad" |
 | @committer | "commit my changes", "generate commit message", "use the committer agent" |
-| @copywriter | "write copy for this page", "conversion strategy", "use the copywriter agent" |
-| @briefing | "create a briefing from plans", "pre-production planning", "frame the problem", "I have an idea but not sure if it's a feature yet", "structure my plans before PRD", "use the briefing agent" |
-| @briefing-refiner | "refine this briefing", "review the briefing before PRD", "create an editable briefing review", "apply briefing refinement feedback" |
-| @genome | "generate a genome", "use the genome agent", "gerar genome" |
+| @copywriter | "write copy for this page", "conversion strategy", "use the copywriter agent" |
+| @briefing | "create a briefing from plans", "pre-production planning", "frame the problem", "I have an idea but not sure if it's a feature yet", "structure my plans before PRD", "use the briefing agent" |
+| @briefing-refiner | "refine this briefing", "review the briefing before PRD", "create an editable briefing review", "apply briefing refinement feedback" |
+| @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" |
@@ -101,8 +101,8 @@ 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`, `@scope-check`, `@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.
+- Official workflow agents (`@setup`, `@product`, `@analyst`, `@scope-check`, `@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. Single exception: when `auto_handoff: true` is set in `project.context.md`, the agents covered by `.aioson/docs/autopilot-handoff.md` auto-invoke the next agent's skill instead of stopping — never past the `@dev` handoff.
 - 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.
@@ -122,9 +122,9 @@ When running Codex directly (without `aioson workflow:next`), these rules apply:
 ## Agent files
 - @setup → `.aioson/agents/setup.md`
 - @discovery-design-doc → `.aioson/agents/discovery-design-doc.md`
-- @analyst → `.aioson/agents/analyst.md`
-- @scope-check → `.aioson/agents/scope-check.md`
-- @architect → `.aioson/agents/architect.md`
+- @analyst → `.aioson/agents/analyst.md`
+- @scope-check → `.aioson/agents/scope-check.md`
+- @architect → `.aioson/agents/architect.md`
 - @ux-ui → `.aioson/agents/ux-ui.md`
 - @product → `.aioson/agents/product.md`
 - @sheldon → `.aioson/agents/sheldon.md`
@@ -137,11 +137,11 @@ When running Codex directly (without `aioson workflow:next`), these rules apply:
 - @neo → `.aioson/agents/neo.md`
 - @orchestrator → `.aioson/agents/orchestrator.md`
 - @squad → `.aioson/agents/squad.md`
-- @committer → `.aioson/agents/committer.md`
-- @copywriter → `.aioson/agents/copywriter.md`
-- @briefing → `.aioson/agents/briefing.md`
-- @briefing-refiner → `.aioson/agents/briefing-refiner.md`
-- @genome → `.aioson/agents/genome.md`
+- @committer → `.aioson/agents/committer.md`
+- @copywriter → `.aioson/agents/copywriter.md`
+- @briefing → `.aioson/agents/briefing.md`
+- @briefing-refiner → `.aioson/agents/briefing-refiner.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`
@@ -179,28 +179,28 @@ Located at: `.aioson/skills/process/aioson-spec-driven/SKILL.md`
 
 This is a first-party process skill. It teaches agents how phases connect, when to apply which depth, and how to prepare clean handoffs.
 
-Agents that load it: @product, @analyst, @scope-check, @architect, @sheldon, @dev, @deyvin, @qa, @tester, @orchestrator, @pm
+Agents that load it: @product, @analyst, @scope-check, @architect, @sheldon, @dev, @deyvin, @qa, @tester, @orchestrator, @pm
 When to load: at the start of any spec work (PRD, requirements, architecture, implementation, testing)
 What to load: `SKILL.md` first, then only the `references/` file relevant to the current phase
 
-## Process skill: design-hybrid-forge
-
-Located at: `.aioson/skills/process/design-hybrid-forge/SKILL.md`
+## Process skill: design-hybrid-forge
+
+Located at: `.aioson/skills/process/design-hybrid-forge/SKILL.md`
 
 This is a first-party process skill for generating project-local hybrid design skills from 2 primary design parents.
 
-Activated by: @design-hybrid-forge
-Default output: `.aioson/installed-skills/{hybrid-name}/`
-What to load: `SKILL.md` first, then only the `references/` file relevant to the current phase
-
-## Process skill: prompt-sharpener
-
-Located at: `.aioson/skills/process/prompt-sharpener/SKILL.md`
-
-This is a first-party process skill for improving agents, skills, PRDs, plans, handoffs, and instruction-heavy markdown by turning vague guidance into evidence-driven decision behavior.
-
-Use when: improving AIOSON prompts/skills, reducing dead context without losing contracts, or sharpening artifacts before downstream handoff.
-What to load: `SKILL.md` first; load `references/prompt-diagnostics.md` only for multi-prompt audits or adoption planning.
+Activated by: @design-hybrid-forge
+Default output: `.aioson/installed-skills/{hybrid-name}/`
+What to load: `SKILL.md` first, then only the `references/` file relevant to the current phase
+
+## Process skill: prompt-sharpener
+
+Located at: `.aioson/skills/process/prompt-sharpener/SKILL.md`
+
+This is a first-party process skill for improving agents, skills, PRDs, plans, handoffs, and instruction-heavy markdown by turning vague guidance into evidence-driven decision behavior.
+
+Use when: improving AIOSON prompts/skills, reducing dead context without losing contracts, or sharpening artifacts before downstream handoff.
+What to load: `SKILL.md` first; load `references/prompt-diagnostics.md` only for multi-prompt audits or adoption planning.
 
 ## Shared research cache: researchs/
 

package/template/CLAUDE.md

@@ -4,29 +4,29 @@ You operate as AIOSON.
 
 ## Mandatory first action
 1. Read `.aioson/config.md`
-2. Check whether `.aioson/context/project.context.md` exists
-   - If missing: run `/setup`
-   - If present: read it before any action
-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.
-
-## Project knowledge
-
-Read `.aioson/learnings/INDEX.md` if it exists. Each line is a project gotcha or recipe with its file path and a one-line summary. Lazy-load individual files only when title/scope matches your current task or files being touched.
-
-## No agent selected
-
-After the mandatory first action, if the user started the chat without naming an agent and has not given a concrete task yet, do not start implementation or workflow routing. First offer these starting lanes:
-
-- Simple Plan with `/dev` for bounded technical work, small fixes, refactors, or directly verifiable implementation.
-- Pair programming with `/deyvin` for continuity, debugging together, or a small validated slice with known context.
-- Briefing with `/briefing` to frame and evaluate an early feature idea before committing to a PRD.
-- Briefing refinement with `/briefing-refiner` to review, annotate, and refine an existing briefing before PRD generation.
-- Product with `/product` to start a full feature definition when the user already wants to build a product/feature.
-
-## Memory loading
-
-Default **ON** in v1.15.0+. Opt out via `AIOSON_OPERATOR_MEMORY=false`.
-
+2. Check whether `.aioson/context/project.context.md` exists
+   - If missing: run `/setup`
+   - If present: read it before any action
+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.
+
+## Project knowledge
+
+Read `.aioson/learnings/INDEX.md` if it exists. Each line is a project gotcha or recipe with its file path and a one-line summary. Lazy-load individual files only when title/scope matches your current task or files being touched.
+
+## No agent selected
+
+After the mandatory first action, if the user started the chat without naming an agent and has not given a concrete task yet, do not start implementation or workflow routing. First offer these starting lanes:
+
+- Simple Plan with `/dev` for bounded technical work, small fixes, refactors, or directly verifiable implementation.
+- Pair programming with `/deyvin` for continuity, debugging together, or a small validated slice with known context.
+- Briefing with `/briefing` to frame and evaluate an early feature idea before committing to a PRD.
+- Briefing refinement with `/briefing-refiner` to review, annotate, and refine an existing briefing before PRD generation.
+- Product with `/product` to start a full feature definition when the user already wants to build a product/feature.
+
+## Memory loading
+
+Default **ON** in v1.15.0+. Opt out via `AIOSON_OPERATOR_MEMORY=false`.
+
 When enabled (default):
 
 1. Read `~/.aioson/operators/{sha256(git-email)[0..16]}/MEMORY.md` if it exists.
@@ -49,9 +49,9 @@ Capture is best-effort — do not crash, retry, or surface failures to the user.
 ## Agents
 - /setup -> `.aioson/agents/setup.md`
 - /discovery-design-doc -> `.aioson/agents/discovery-design-doc.md`
-- /analyst -> `.aioson/agents/analyst.md`
-- /scope-check -> `.aioson/agents/scope-check.md`
-- /architect -> `.aioson/agents/architect.md`
+- /analyst -> `.aioson/agents/analyst.md`
+- /scope-check -> `.aioson/agents/scope-check.md`
+- /architect -> `.aioson/agents/architect.md`
 - /ux-ui (UI/UX) -> `.aioson/agents/ux-ui.md`
 - /product -> `.aioson/agents/product.md`
 - /sheldon -> `.aioson/agents/sheldon.md`
@@ -66,11 +66,11 @@ Capture is best-effort — do not crash, retry, or surface failures to the user.
 - /neo -> `.aioson/agents/neo.md`
 - /orchestrator -> `.aioson/agents/orchestrator.md`
 - /squad -> `.aioson/agents/squad.md`
-- /committer -> `.aioson/agents/committer.md`
-- /copywriter -> `.aioson/agents/copywriter.md`
-- /briefing -> `.aioson/agents/briefing.md`
-- /briefing-refiner -> `.aioson/agents/briefing-refiner.md`
-- /orache -> `.aioson/agents/orache.md`
+- /committer -> `.aioson/agents/committer.md`
+- /copywriter -> `.aioson/agents/copywriter.md`
+- /briefing -> `.aioson/agents/briefing.md`
+- /briefing-refiner -> `.aioson/agents/briefing-refiner.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`
@@ -89,7 +89,7 @@ AIOSON follows a Spec-Driven Development (SDD) methodology. Key governance files
 
 The process depth scales with project classification:
 - **MICRO** (0-1): lightweight — @product → @dev
-- **SMALL** (2-3): standard — @product → @analyst → @scope-check(pre-dev) → @architect → @discovery-design-doc → @dev, with optional @scope-check(post-dev) before @qa when implementation drift is likely
+- **SMALL** (2-3): standard — @product → @analyst → @scope-check(pre-dev) → @architect → @discovery-design-doc → @dev, with optional @scope-check(post-dev) before @qa when implementation drift is likely
 - **MEDIUM** (4-6): full — all agents, all gates, all artifacts
 
 Classification is determined by @analyst during discovery. See `aioson-spec-driven` skill for details.
@@ -103,7 +103,7 @@ When running Claude Code directly (without `aioson workflow:next`), these rules
 **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.
+- Between agent handoffs, your ONLY valid output is: which agent is next and why. Do not continue into that agent's work. Single exception: when `auto_handoff: true` is set in `project.context.md`, the agents covered by `.aioson/docs/autopilot-handoff.md` auto-invoke the next agent's skill instead of stopping — never past the `@dev` handoff.
 - 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.