sagaz-ai 0.1.0

package/ai-orchestration-ecosystem/squads/github-ops.md

@@ -0,0 +1,45 @@
+# Squad: Github Ops
+
+## Use
+
+Use this squad when the task matches Github Ops.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/maintenance-ops.md

@@ -0,0 +1,45 @@
+# Squad: Maintenance Ops
+
+## Use
+
+Use this squad when the task matches Maintenance Ops.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/mobile-app-studio.md

@@ -0,0 +1,45 @@
+# Squad: Mobile App Studio
+
+## Use
+
+Use this squad when the task matches Mobile App Studio.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/product-factory.md

@@ -0,0 +1,45 @@
+# Squad: Product Factory
+
+## Use
+
+Use this squad when the task matches Product Factory.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/production-critical.md

@@ -0,0 +1,45 @@
+# Squad: Production Critical
+
+## Use
+
+Use this squad when the task matches Production Critical.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/refactor-lab.md

@@ -0,0 +1,45 @@
+# Squad: Refactor Lab
+
+## Use
+
+Use this squad when the task matches Refactor Lab.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/squads/research-to-spec.md

@@ -0,0 +1,45 @@
+# Squad: Research To Spec
+
+## Use
+
+Use this squad when the task matches Research To Spec.
+
+## Agents
+
+- Orchestrator
+- Product Strategist when product decisions are needed
+- Technology Strategist when stack or deployment decisions are needed
+- Software Architect when architecture matters
+- Design Studio roles when UI exists
+- Implementation Engineer when code changes are needed
+- QA Verifier for verification
+- Security Governance when data, auth, secrets, payments, or production are involved
+- GitHub Ops when versioning, PRs, releases, or checks are useful
+
+## Flow
+
+1. Confirm objective, constraints, definition of done, and risks.
+2. Select relevant tasks and protocols.
+3. Execute the phase in small verifiable steps.
+4. Produce evidence and residual risks.
+5. Ask permission before handing off to the next team.
+
+## Required Gates
+
+- Clear objective and definition of done.
+- Relevant specification or task contract.
+- Handoff approval between major phases.
+- Verification evidence proportional to risk.
+- Residual risks documented.
+
+## Standard Output
+
+```md
+Scope:
+Current phase:
+Evidence:
+Risks:
+Next team:
+Permission request:
+```
+

package/ai-orchestration-ecosystem/tasks/design-system.md

@@ -0,0 +1,34 @@
+# Task: Design System
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/github-release-ops.md

@@ -0,0 +1,34 @@
+# Task: Github Release Ops
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/implementation-build.md

@@ -0,0 +1,34 @@
+# Task: Implementation Build
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/intake-brief.md

@@ -0,0 +1,34 @@
+# Task: Intake Brief
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/product-requirements.md

@@ -0,0 +1,34 @@
+# Task: Product Requirements
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/production-readiness.md

@@ -0,0 +1,34 @@
+# Task: Production Readiness
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/stack-recommendation.md

@@ -0,0 +1,34 @@
+# Task: Stack Recommendation
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/tasks/verification-qa.md

@@ -0,0 +1,34 @@
+# Task: Verification Qa
+
+## Owner
+
+Assigned by the active workflow or squad.
+
+## Inputs
+
+- User goal.
+- Current run state.
+- Relevant specifications, files, and constraints.
+
+## Outputs
+
+- Completed task artifact.
+- Evidence.
+- Risks and pending items.
+- Handoff recommendation.
+
+## Acceptance Criteria
+
+- Output is specific and testable.
+- Assumptions are recorded.
+- Verification method is stated.
+- Next step is clear.
+
+## Verification
+
+Check against the active protocol and quality gates.
+
+## Stop Condition
+
+Stop and ask the user when scope, cost, architecture, production risk, or external state would change.
+

package/ai-orchestration-ecosystem/templates/design-system-spec.md

@@ -0,0 +1,20 @@
+# Design System Spec
+
+## Objective
+
+## Context
+
+## Inputs
+
+## Decisions
+
+## Outputs
+
+## Evidence
+
+## Risks
+
+## Next Step
+
+## User Permission
+

package/ai-orchestration-ecosystem/templates/final-handoff.md

@@ -0,0 +1,20 @@
+# Final Handoff
+
+## Objective
+
+## Context
+
+## Inputs
+
+## Decisions
+
+## Outputs
+
+## Evidence
+
+## Risks
+
+## Next Step
+
+## User Permission
+

package/ai-orchestration-ecosystem/templates/github-actions-checklist.md

@@ -0,0 +1,20 @@
+# Github Actions Checklist
+
+## Objective
+
+## Context
+
+## Inputs
+
+## Decisions
+
+## Outputs
+
+## Evidence
+
+## Risks
+
+## Next Step
+
+## User Permission
+

package/ai-orchestration-ecosystem/templates/implementation-plan.md

@@ -0,0 +1,20 @@
+# Implementation Plan
+
+## Objective
+
+## Context
+
+## Inputs
+
+## Decisions
+
+## Outputs
+
+## Evidence
+
+## Risks
+
+## Next Step
+
+## User Permission
+

package/ai-orchestration-ecosystem/templates/mobile-release-checklist.md

@@ -0,0 +1,20 @@
+# Mobile Release Checklist
+
+## Objective
+
+## Context
+
+## Inputs
+
+## Decisions
+
+## Outputs
+
+## Evidence
+
+## Risks
+
+## Next Step
+
+## User Permission
+