sagaz-ai 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/INSTALL.md +78 -0
- package/LICENSE +21 -0
- package/README.md +185 -0
- package/ai-orchestration-ecosystem/ACTIVATE.md +45 -0
- package/ai-orchestration-ecosystem/INDEX.md +73 -0
- package/ai-orchestration-ecosystem/README.md +31 -0
- package/ai-orchestration-ecosystem/agents/design-director.md +20 -0
- package/ai-orchestration-ecosystem/agents/implementation-engineer.md +21 -0
- package/ai-orchestration-ecosystem/agents/orchestrator.md +22 -0
- package/ai-orchestration-ecosystem/agents/product-strategist.md +22 -0
- package/ai-orchestration-ecosystem/agents/qa-verifier.md +23 -0
- package/ai-orchestration-ecosystem/agents/refactor-steward.md +20 -0
- package/ai-orchestration-ecosystem/agents/security-governance.md +21 -0
- package/ai-orchestration-ecosystem/agents/software-architect.md +21 -0
- package/ai-orchestration-ecosystem/agents/specification-writer.md +21 -0
- package/ai-orchestration-ecosystem/agents/technology-strategist.md +21 -0
- package/ai-orchestration-ecosystem/agents/ui-systems-designer.md +20 -0
- package/ai-orchestration-ecosystem/agents/ux-architect.md +21 -0
- package/ai-orchestration-ecosystem/agents/visual-qa.md +20 -0
- package/ai-orchestration-ecosystem/core/decision-records.md +25 -0
- package/ai-orchestration-ecosystem/core/operating-system.md +29 -0
- package/ai-orchestration-ecosystem/core/token-economy.md +15 -0
- package/ai-orchestration-ecosystem/engineering/software-engineering-deep-guide.md +23 -0
- package/ai-orchestration-ecosystem/governance/ecosystem-maintenance.md +13 -0
- package/ai-orchestration-ecosystem/governance/package-release-policy.md +51 -0
- package/ai-orchestration-ecosystem/governance/quality-policy.md +13 -0
- package/ai-orchestration-ecosystem/governance/security-policy.md +13 -0
- package/ai-orchestration-ecosystem/governance/versioning.md +13 -0
- package/ai-orchestration-ecosystem/protocols/accessibility-compliance.md +39 -0
- package/ai-orchestration-ecosystem/protocols/ai-application-quality.md +40 -0
- package/ai-orchestration-ecosystem/protocols/api-contracts.md +37 -0
- package/ai-orchestration-ecosystem/protocols/architecture-fitness-functions.md +36 -0
- package/ai-orchestration-ecosystem/protocols/ci-cd-readiness.md +32 -0
- package/ai-orchestration-ecosystem/protocols/communication.md +32 -0
- package/ai-orchestration-ecosystem/protocols/data-privacy-lifecycle.md +38 -0
- package/ai-orchestration-ecosystem/protocols/database-migrations.md +36 -0
- package/ai-orchestration-ecosystem/protocols/delegation.md +32 -0
- package/ai-orchestration-ecosystem/protocols/dependency-governance.md +36 -0
- package/ai-orchestration-ecosystem/protocols/design-quality.md +32 -0
- package/ai-orchestration-ecosystem/protocols/dora-metrics.md +36 -0
- package/ai-orchestration-ecosystem/protocols/github-operations.md +32 -0
- package/ai-orchestration-ecosystem/protocols/guided-proactivity.md +32 -0
- package/ai-orchestration-ecosystem/protocols/memory.md +32 -0
- package/ai-orchestration-ecosystem/protocols/model-routing.md +32 -0
- package/ai-orchestration-ecosystem/protocols/performance-budgets.md +41 -0
- package/ai-orchestration-ecosystem/protocols/post-delivery-monitoring.md +32 -0
- package/ai-orchestration-ecosystem/protocols/production-readiness.md +32 -0
- package/ai-orchestration-ecosystem/protocols/quality-gates.md +32 -0
- package/ai-orchestration-ecosystem/protocols/release-strategy.md +38 -0
- package/ai-orchestration-ecosystem/protocols/secure-sdlc.md +38 -0
- package/ai-orchestration-ecosystem/protocols/squad-pipeline-handoffs.md +32 -0
- package/ai-orchestration-ecosystem/protocols/sre-readiness.md +41 -0
- package/ai-orchestration-ecosystem/protocols/stack-selection.md +32 -0
- package/ai-orchestration-ecosystem/protocols/testing-matrix.md +32 -0
- package/ai-orchestration-ecosystem/quickstart.md +25 -0
- package/ai-orchestration-ecosystem/skills/exhaustive-verification.md +14 -0
- package/ai-orchestration-ecosystem/skills/refactor-proofing.md +14 -0
- package/ai-orchestration-ecosystem/skills/spec-first-development.md +14 -0
- package/ai-orchestration-ecosystem/squads/code-audit.md +45 -0
- package/ai-orchestration-ecosystem/squads/design-studio.md +45 -0
- package/ai-orchestration-ecosystem/squads/github-ops.md +45 -0
- package/ai-orchestration-ecosystem/squads/maintenance-ops.md +45 -0
- package/ai-orchestration-ecosystem/squads/mobile-app-studio.md +45 -0
- package/ai-orchestration-ecosystem/squads/product-factory.md +45 -0
- package/ai-orchestration-ecosystem/squads/production-critical.md +45 -0
- package/ai-orchestration-ecosystem/squads/refactor-lab.md +45 -0
- package/ai-orchestration-ecosystem/squads/research-to-spec.md +45 -0
- package/ai-orchestration-ecosystem/tasks/design-system.md +34 -0
- package/ai-orchestration-ecosystem/tasks/github-release-ops.md +34 -0
- package/ai-orchestration-ecosystem/tasks/implementation-build.md +34 -0
- package/ai-orchestration-ecosystem/tasks/intake-brief.md +34 -0
- package/ai-orchestration-ecosystem/tasks/product-requirements.md +34 -0
- package/ai-orchestration-ecosystem/tasks/production-readiness.md +34 -0
- package/ai-orchestration-ecosystem/tasks/stack-recommendation.md +34 -0
- package/ai-orchestration-ecosystem/tasks/verification-qa.md +34 -0
- package/ai-orchestration-ecosystem/templates/design-system-spec.md +20 -0
- package/ai-orchestration-ecosystem/templates/final-handoff.md +20 -0
- package/ai-orchestration-ecosystem/templates/github-actions-checklist.md +20 -0
- package/ai-orchestration-ecosystem/templates/implementation-plan.md +20 -0
- package/ai-orchestration-ecosystem/templates/mobile-release-checklist.md +20 -0
- package/ai-orchestration-ecosystem/templates/product-spec.md +20 -0
- package/ai-orchestration-ecosystem/templates/qa-report.md +20 -0
- package/ai-orchestration-ecosystem/templates/run-state.md +20 -0
- package/ai-orchestration-ecosystem/templates/squad-handoff.md +20 -0
- package/ai-orchestration-ecosystem/templates/squad-runbook.md +20 -0
- package/ai-orchestration-ecosystem/templates/stack-recommendation.md +20 -0
- package/ai-orchestration-ecosystem/templates/task-brief.md +20 -0
- package/ai-orchestration-ecosystem/templates/technical-spec.md +20 -0
- package/ai-orchestration-ecosystem/workflows/brownfield-refactor-safe.md +25 -0
- package/ai-orchestration-ecosystem/workflows/bugfix-to-release.md +25 -0
- package/ai-orchestration-ecosystem/workflows/greenfield-web-app.md +25 -0
- package/ai-orchestration-ecosystem/workflows/mobile-app-production.md +36 -0
- package/ai-orchestration-ecosystem/workflows/web-production-release.md +39 -0
- package/bin/sagaz.js +107 -0
- package/codex-skill/sagaz/SKILL.md +69 -0
- package/package.json +42 -0
- package/scripts/verify-package.js +29 -0
package/INSTALL.md
ADDED
|
@@ -0,0 +1,78 @@
|
|
|
1
|
+
# Sagaz Installation
|
|
2
|
+
|
|
3
|
+
## Requirements
|
|
4
|
+
|
|
5
|
+
- Codex Desktop.
|
|
6
|
+
- Node.js 18+ if installing with `npx`.
|
|
7
|
+
- Git installed.
|
|
8
|
+
- GitHub CLI (`gh`) installed and authenticated if you want GitHub Ops.
|
|
9
|
+
- Access to the local Codex skills folder.
|
|
10
|
+
|
|
11
|
+
## Recommended: Install With npx
|
|
12
|
+
|
|
13
|
+
```powershell
|
|
14
|
+
npx sagaz-ai install
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
Then open a new Codex Desktop thread and test:
|
|
18
|
+
|
|
19
|
+
```text
|
|
20
|
+
Sagaz: explain the available workflows.
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Optional Commands
|
|
24
|
+
|
|
25
|
+
```powershell
|
|
26
|
+
npx sagaz-ai status
|
|
27
|
+
npx sagaz-ai doctor
|
|
28
|
+
npx sagaz-ai install --force
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
To also copy the ecosystem to a chosen folder:
|
|
32
|
+
|
|
33
|
+
```powershell
|
|
34
|
+
npx sagaz-ai install --ecosystem C:\Users\YOUR_USER\Documents\Sagaz\ai-orchestration-ecosystem
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
## Manual Install
|
|
38
|
+
|
|
39
|
+
Copy:
|
|
40
|
+
|
|
41
|
+
```text
|
|
42
|
+
codex-skill\sagaz
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
into:
|
|
46
|
+
|
|
47
|
+
```text
|
|
48
|
+
C:\Users\YOUR_USER\.codex\skills\sagaz
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
Then open a new Codex Desktop thread and test:
|
|
52
|
+
|
|
53
|
+
```text
|
|
54
|
+
Sagaz: explain the available workflows.
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
## Use In A Project
|
|
58
|
+
|
|
59
|
+
Keep this repository available to Codex. Then, inside the project you want to work on, ask:
|
|
60
|
+
|
|
61
|
+
```text
|
|
62
|
+
Sagaz: use the appropriate workflow for this project. Maintain run state, handoffs, and verification evidence.
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
## GitHub Ops
|
|
66
|
+
|
|
67
|
+
Authenticate GitHub CLI:
|
|
68
|
+
|
|
69
|
+
```powershell
|
|
70
|
+
gh auth login -h github.com
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Verify:
|
|
74
|
+
|
|
75
|
+
```powershell
|
|
76
|
+
gh auth status
|
|
77
|
+
git --version
|
|
78
|
+
```
|
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Thiago Cabral
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,185 @@
|
|
|
1
|
+
# Sagaz
|
|
2
|
+
|
|
3
|
+
Sagaz is a local AI orchestration ecosystem designed for Codex Desktop. It turns a product request into a structured delivery process with specialized AI teams, explicit handoffs, detailed specifications, implementation, testing, high-standard UX/UI, guided GitHub operations, CI/CD readiness, and production-quality gates.
|
|
4
|
+
|
|
5
|
+
It is inspired by ideas from AIOX, CrewAI, AutoGen, LangChain, and enterprise governance platforms, but it is designed for one practical goal: make Codex Desktop easy to use for serious web and mobile software projects while keeping token usage low and technical quality high.
|
|
6
|
+
|
|
7
|
+
## Designed For Codex Desktop
|
|
8
|
+
|
|
9
|
+
Sagaz is intended to be used inside Codex Desktop the way this repository was created: as a local Codex skill plus a Markdown orchestration ecosystem. The npm package only installs the skill and ecosystem files. It is not a standalone terminal agent runtime and it is not a replacement for Codex CLI.
|
|
10
|
+
|
|
11
|
+
## What Sagaz Does
|
|
12
|
+
|
|
13
|
+
Sagaz organizes work into focused teams:
|
|
14
|
+
|
|
15
|
+
- Product strategy and requirements.
|
|
16
|
+
- Stack recommendation.
|
|
17
|
+
- Software architecture.
|
|
18
|
+
- UX, UI, and design systems.
|
|
19
|
+
- Implementation.
|
|
20
|
+
- QA and testing.
|
|
21
|
+
- Security and production readiness.
|
|
22
|
+
- GitHub commits, pull requests, issues, releases, and checks.
|
|
23
|
+
- Android/iOS mobile delivery.
|
|
24
|
+
- CI/CD and post-delivery monitoring.
|
|
25
|
+
|
|
26
|
+
Sagaz also guides the user through the process. At the end of each phase, it explains what was completed, which team should work next, why the next step matters, and asks permission before moving forward.
|
|
27
|
+
|
|
28
|
+
## Why Use Sagaz
|
|
29
|
+
|
|
30
|
+
- **Simple invocation:** start with `Sagaz:` and describe the goal.
|
|
31
|
+
- **Low token usage:** load only the workflow, squad, task, or protocol needed for the current phase.
|
|
32
|
+
- **Guided process:** team handoffs require user approval.
|
|
33
|
+
- **Production quality:** gates for tests, security, builds, deployment, rollback, and residual risk.
|
|
34
|
+
- **Premium design:** UX/UI, design systems, responsiveness, accessibility, and visual QA.
|
|
35
|
+
- **Stack advisory:** technology choices explained by cost, speed, scale, maintainability, deployment, and future changes.
|
|
36
|
+
- **GitHub without guesswork:** Sagaz recommends commits, pushes, pull requests, issues, and releases at the right time.
|
|
37
|
+
- **Web and mobile:** workflows for browser apps, websites, dashboards, Android, and iOS.
|
|
38
|
+
- **Persistent state:** Markdown run state records decisions, approvals, handoffs, risks, and test evidence.
|
|
39
|
+
|
|
40
|
+
## How It Works
|
|
41
|
+
|
|
42
|
+
Sagaz uses Markdown files as the source of truth. The main structure is:
|
|
43
|
+
|
|
44
|
+
```text
|
|
45
|
+
ai-orchestration-ecosystem/
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Key areas:
|
|
49
|
+
|
|
50
|
+
- `workflows/`: ready-made workflows for web, mobile, production, bug fixes, and refactoring.
|
|
51
|
+
- `squads/`: specialized teams.
|
|
52
|
+
- `agents/`: individual roles.
|
|
53
|
+
- `tasks/`: formal tasks with inputs, outputs, acceptance criteria, verification, and stop conditions.
|
|
54
|
+
- `protocols/`: rules for quality, handoffs, GitHub, production, design, CI/CD, and monitoring.
|
|
55
|
+
- `templates/`: reusable artifacts for specs, QA, handoffs, run state, and releases.
|
|
56
|
+
- `engineering/`: deep software engineering standards.
|
|
57
|
+
- `governance/`: security, quality, versioning, and ecosystem maintenance.
|
|
58
|
+
|
|
59
|
+
## Included Workflows
|
|
60
|
+
|
|
61
|
+
- `greenfield-web-app`: create a website or web app from scratch.
|
|
62
|
+
- `web-production-release`: prepare a web app for production.
|
|
63
|
+
- `mobile-app-production`: create or prepare an Android/iOS app.
|
|
64
|
+
- `brownfield-refactor-safe`: refactor an existing project safely.
|
|
65
|
+
- `bugfix-to-release`: fix a bug through verification and release.
|
|
66
|
+
|
|
67
|
+
## Installation In Codex Desktop
|
|
68
|
+
|
|
69
|
+
### Recommended: Install With npx
|
|
70
|
+
|
|
71
|
+
```powershell
|
|
72
|
+
npx sagaz-ai install
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Then open a new Codex Desktop thread and run:
|
|
76
|
+
|
|
77
|
+
```text
|
|
78
|
+
Sagaz: explain the available workflows.
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
Optional: also copy the ecosystem to a known local folder:
|
|
82
|
+
|
|
83
|
+
```powershell
|
|
84
|
+
npx sagaz-ai install --ecosystem C:\Users\YOUR_USER\Documents\Sagaz\ai-orchestration-ecosystem
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
Check installation:
|
|
88
|
+
|
|
89
|
+
```powershell
|
|
90
|
+
npx sagaz-ai status
|
|
91
|
+
npx sagaz-ai doctor
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
### Manual Installation
|
|
95
|
+
|
|
96
|
+
#### 1. Clone Or Download The Repository
|
|
97
|
+
|
|
98
|
+
```powershell
|
|
99
|
+
git clone https://github.com/tscabral1/sagaz.git
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
Or download the ZIP from GitHub.
|
|
103
|
+
|
|
104
|
+
#### 2. Copy The Skill Into Codex
|
|
105
|
+
|
|
106
|
+
On Windows, the local Codex skills folder is usually:
|
|
107
|
+
|
|
108
|
+
```text
|
|
109
|
+
C:\Users\YOUR_USER\.codex\skills
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
Copy this folder:
|
|
113
|
+
|
|
114
|
+
```text
|
|
115
|
+
codex-skill\sagaz
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
into:
|
|
119
|
+
|
|
120
|
+
```text
|
|
121
|
+
C:\Users\YOUR_USER\.codex\skills\sagaz
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
#### 3. Keep The Ecosystem Available
|
|
125
|
+
|
|
126
|
+
Keep `ai-orchestration-ecosystem/` accessible in the Codex workspace or in a known local folder.
|
|
127
|
+
|
|
128
|
+
#### 4. open a new Codex Desktop thread
|
|
129
|
+
|
|
130
|
+
After copying the skill, open a new Codex Desktop thread so Codex can discover the updated skill.
|
|
131
|
+
|
|
132
|
+
## How To Use
|
|
133
|
+
|
|
134
|
+
Use a simple prompt:
|
|
135
|
+
|
|
136
|
+
```text
|
|
137
|
+
Sagaz: create a complete website for my company, from planning to deployment.
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
Or:
|
|
141
|
+
|
|
142
|
+
```text
|
|
143
|
+
Sagaz: create an Android/iOS app for personal finance tracking, with premium design, tests, and production readiness.
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
Sagaz should choose the appropriate workflow, create or update persistent run state, recommend a stack, plan requirements, create UX/UI and a design system, implement, test, prepare production and CI/CD, suggest GitHub operations, and deliver a final handoff with evidence and risks.
|
|
147
|
+
|
|
148
|
+
For production-grade work, Sagaz can also apply SRE readiness, DORA metrics, secure SDLC, dependency governance, data privacy lifecycle, architecture fitness functions, API contracts, performance budgets, accessibility compliance, database migrations, release strategy, and AI application quality protocols.
|
|
149
|
+
|
|
150
|
+
## Web Example
|
|
151
|
+
|
|
152
|
+
```text
|
|
153
|
+
Sagaz: I want to create a web SaaS for appointment scheduling.
|
|
154
|
+
|
|
155
|
+
Requirements:
|
|
156
|
+
- user login
|
|
157
|
+
- calendar
|
|
158
|
+
- admin dashboard
|
|
159
|
+
- premium design
|
|
160
|
+
- production-ready
|
|
161
|
+
- deployment on Vercel
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
## Mobile Example
|
|
165
|
+
|
|
166
|
+
```text
|
|
167
|
+
Sagaz: I want to create an Android/iOS app for daily habit tracking.
|
|
168
|
+
|
|
169
|
+
Recommend the stack, explain costs, create mobile UX, implement it, test it, and prepare the release checklist.
|
|
170
|
+
```
|
|
171
|
+
|
|
172
|
+
## Important Rules
|
|
173
|
+
|
|
174
|
+
Sagaz must ask permission before moving between major teams/phases, installing dependencies, creating or editing files when implementation has not been clearly authorized, deploying, creating a repository, committing, pushing, opening a PR, creating an issue/tag/release, accepting high risk, or running destructive actions.
|
|
175
|
+
|
|
176
|
+
Sagaz may directly run low-risk diagnostics such as reading files, inspecting structure, searching text, checking status, and proposing plans.
|
|
177
|
+
|
|
178
|
+
## Who It Is For
|
|
179
|
+
|
|
180
|
+
Sagaz is for users who want to build serious software with Codex without needing to personally manage every detail of engineering, design, GitHub, deployment, and production operations.
|
|
181
|
+
|
|
182
|
+
## Status
|
|
183
|
+
|
|
184
|
+
Sagaz is an evolving local orchestration ecosystem. The source of truth is the Markdown in this repository.
|
|
185
|
+
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
# Activate Sagaz Ecosystem
|
|
2
|
+
|
|
3
|
+
## Short Invocation
|
|
4
|
+
|
|
5
|
+
```text
|
|
6
|
+
Sagaz: [your task]
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
## Full Invocation
|
|
10
|
+
|
|
11
|
+
```text
|
|
12
|
+
Activate the Sagaz AI Orchestration Ecosystem.
|
|
13
|
+
Read only ai-orchestration-ecosystem/quickstart.md first.
|
|
14
|
+
Choose the smallest sufficient mode, workflow, and squad.
|
|
15
|
+
Use detailed specifications when risk justifies it.
|
|
16
|
+
Validate with quality gates and the testing matrix.
|
|
17
|
+
Use low token context and save important artifacts in Markdown.
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
## Common Uses
|
|
21
|
+
|
|
22
|
+
### New Product
|
|
23
|
+
|
|
24
|
+
```text
|
|
25
|
+
Sagaz: use the product-factory squad to create this product from planning through delivery.
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
### High-Standard Design
|
|
29
|
+
|
|
30
|
+
```text
|
|
31
|
+
Sagaz: use design-studio to create a premium UX/UI with a complete design system, responsiveness, accessibility, and visual QA.
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
### Guided GitHub
|
|
35
|
+
|
|
36
|
+
```text
|
|
37
|
+
Sagaz: proactively handle Git and GitHub for this project. Explain why each action matters and ask permission before running it.
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
### Pipeline With Handoffs
|
|
41
|
+
|
|
42
|
+
```text
|
|
43
|
+
Sagaz: follow a sequential pipeline with team handoffs. At the end of each phase, explain what was done, what the next team will do, and ask permission before moving forward.
|
|
44
|
+
```
|
|
45
|
+
|
|
@@ -0,0 +1,73 @@
|
|
|
1
|
+
# Index
|
|
2
|
+
|
|
3
|
+
## Quick Entry
|
|
4
|
+
|
|
5
|
+
- `ACTIVATE.md`: ready-to-use activation prompts.
|
|
6
|
+
- `quickstart.md`: minimum operating rules.
|
|
7
|
+
- `README.md`: ecosystem overview.
|
|
8
|
+
|
|
9
|
+
## Core
|
|
10
|
+
|
|
11
|
+
- `core/operating-system.md`
|
|
12
|
+
- `core/token-economy.md`
|
|
13
|
+
- `core/decision-records.md`
|
|
14
|
+
|
|
15
|
+
## Engineering
|
|
16
|
+
|
|
17
|
+
- `engineering/software-engineering-deep-guide.md`
|
|
18
|
+
|
|
19
|
+
## Workflows
|
|
20
|
+
|
|
21
|
+
- `workflows/greenfield-web-app.md`
|
|
22
|
+
- `workflows/web-production-release.md`
|
|
23
|
+
- `workflows/mobile-app-production.md`
|
|
24
|
+
- `workflows/brownfield-refactor-safe.md`
|
|
25
|
+
- `workflows/bugfix-to-release.md`
|
|
26
|
+
|
|
27
|
+
## Squads
|
|
28
|
+
|
|
29
|
+
- `squads/product-factory.md`
|
|
30
|
+
- `squads/design-studio.md`
|
|
31
|
+
- `squads/mobile-app-studio.md`
|
|
32
|
+
- `squads/production-critical.md`
|
|
33
|
+
- `squads/github-ops.md`
|
|
34
|
+
- `squads/code-audit.md`
|
|
35
|
+
- `squads/refactor-lab.md`
|
|
36
|
+
- `squads/research-to-spec.md`
|
|
37
|
+
- `squads/maintenance-ops.md`
|
|
38
|
+
|
|
39
|
+
## Agents
|
|
40
|
+
|
|
41
|
+
See `agents/` for Orchestrator, Product Strategist, Technology Strategist, Software Architect, Implementation Engineer, QA Verifier, Security Governance, Design Director, UX Architect, UI Systems Designer, Visual QA, Specification Writer, and Refactor Steward.
|
|
42
|
+
|
|
43
|
+
## Protocols
|
|
44
|
+
|
|
45
|
+
See `protocols/` for quality gates, testing matrix, stack selection, design quality, guided proactivity, squad handoffs, production readiness, GitHub operations, CI/CD readiness, post-delivery monitoring, delegation, communication, memory, and model routing.
|
|
46
|
+
|
|
47
|
+
## Advanced Engineering Protocols
|
|
48
|
+
|
|
49
|
+
- `protocols/sre-readiness.md`
|
|
50
|
+
- `protocols/dora-metrics.md`
|
|
51
|
+
- `protocols/secure-sdlc.md`
|
|
52
|
+
- `protocols/dependency-governance.md`
|
|
53
|
+
- `protocols/data-privacy-lifecycle.md`
|
|
54
|
+
- `protocols/architecture-fitness-functions.md`
|
|
55
|
+
- `protocols/api-contracts.md`
|
|
56
|
+
- `protocols/performance-budgets.md`
|
|
57
|
+
- `protocols/accessibility-compliance.md`
|
|
58
|
+
- `protocols/database-migrations.md`
|
|
59
|
+
- `protocols/release-strategy.md`
|
|
60
|
+
- `protocols/ai-application-quality.md`
|
|
61
|
+
|
|
62
|
+
## Templates
|
|
63
|
+
|
|
64
|
+
See `templates/` for task briefs, product specs, technical specs, design systems, stack recommendations, run state, squad handoffs, QA reports, release checklists, and final handoffs.
|
|
65
|
+
|
|
66
|
+
## Governance
|
|
67
|
+
|
|
68
|
+
- `governance/quality-policy.md`
|
|
69
|
+
- `governance/security-policy.md`
|
|
70
|
+
- `governance/versioning.md`
|
|
71
|
+
- `governance/ecosystem-maintenance.md`
|
|
72
|
+
- `governance/package-release-policy.md`
|
|
73
|
+
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# Sagaz AI Orchestration Ecosystem
|
|
2
|
+
|
|
3
|
+
A local AI orchestration ecosystem for Codex, focused on autonomous teams, consistent outcomes, low token usage, high-quality software engineering, premium UX/UI, and production-ready delivery.
|
|
4
|
+
|
|
5
|
+
## How To Use
|
|
6
|
+
|
|
7
|
+
1. Read `quickstart.md`.
|
|
8
|
+
2. Choose the smallest sufficient workflow or squad.
|
|
9
|
+
3. Use formal tasks, handoffs, and quality gates.
|
|
10
|
+
4. Create or update run state for medium/large work.
|
|
11
|
+
5. Verify before declaring done.
|
|
12
|
+
|
|
13
|
+
## Structure
|
|
14
|
+
|
|
15
|
+
- `workflows/`: named end-to-end flows.
|
|
16
|
+
- `squads/`: specialized teams.
|
|
17
|
+
- `agents/`: role definitions.
|
|
18
|
+
- `tasks/`: formal task contracts.
|
|
19
|
+
- `protocols/`: operating rules and quality gates.
|
|
20
|
+
- `templates/`: reusable Markdown artifacts.
|
|
21
|
+
- `engineering/`: software engineering standards.
|
|
22
|
+
- `governance/`: quality, security, and maintenance policies.
|
|
23
|
+
|
|
24
|
+
## Golden Rule
|
|
25
|
+
|
|
26
|
+
No delivery is complete without verification evidence proportional to the risk.
|
|
27
|
+
|
|
28
|
+
## Advanced Engineering Coverage
|
|
29
|
+
|
|
30
|
+
Sagaz includes protocols for SRE readiness, DORA metrics, secure SDLC, dependency governance, data privacy lifecycle, architecture fitness functions, API contracts, performance budgets, accessibility compliance, database migrations, release strategy, and AI application quality.
|
|
31
|
+
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Agent: Design Director
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Set visual direction and ensure the interface reaches a high market-standard quality bar.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Interpret domain, audience, and positioning.
|
|
10
|
+
- Define visual personality.
|
|
11
|
+
- Enforce hierarchy, composition, rhythm, and polish.
|
|
12
|
+
- Block generic or visually weak interfaces.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Visual direction
|
|
17
|
+
- Interface principles
|
|
18
|
+
- Design risks
|
|
19
|
+
- Visual acceptance criteria
|
|
20
|
+
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Agent: Implementation Engineer
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Implement scoped changes while respecting existing patterns and keeping verification practical.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Inspect the repository before editing.
|
|
10
|
+
- Follow local conventions.
|
|
11
|
+
- Make small verifiable changes.
|
|
12
|
+
- Avoid unrelated refactors.
|
|
13
|
+
- Document changed files and reasons.
|
|
14
|
+
|
|
15
|
+
## Standard Output
|
|
16
|
+
|
|
17
|
+
- Implementation summary
|
|
18
|
+
- Changed files
|
|
19
|
+
- How to run
|
|
20
|
+
- Notes for future work
|
|
21
|
+
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# Agent: Orchestrator
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Turn user goals into an executable plan, select the smallest sufficient team, manage handoffs, and enforce quality gates.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Clarify objective, constraints, definition of done, and risks.
|
|
10
|
+
- Select workflow, squad, and autonomy level.
|
|
11
|
+
- Break work into verifiable phases.
|
|
12
|
+
- Ask permission before meaningful handoffs or state-changing actions.
|
|
13
|
+
- Require evidence before declaring work complete.
|
|
14
|
+
|
|
15
|
+
## Standard Output
|
|
16
|
+
|
|
17
|
+
- Plan
|
|
18
|
+
- Delegations
|
|
19
|
+
- Handoff requests
|
|
20
|
+
- Quality gate summary
|
|
21
|
+
- Final report
|
|
22
|
+
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
# Agent: Product Strategist
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Translate broad intent into product scope, user journeys, requirements, and acceptance criteria.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Define target users and primary jobs to be done.
|
|
10
|
+
- Separate essential scope from optional scope.
|
|
11
|
+
- Write functional and non-functional requirements.
|
|
12
|
+
- Identify success metrics and product risks.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Product goal
|
|
17
|
+
- Users
|
|
18
|
+
- Use cases
|
|
19
|
+
- Requirements
|
|
20
|
+
- Acceptance criteria
|
|
21
|
+
- Product risks
|
|
22
|
+
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Agent: Qa Verifier
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Prove that the delivery works, expose regressions, and document residual risks.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Create a test matrix proportional to risk.
|
|
10
|
+
- Run relevant automated checks.
|
|
11
|
+
- Perform smoke tests for primary flows.
|
|
12
|
+
- Test edge cases, empty states, and error states.
|
|
13
|
+
- Block fragile deliveries.
|
|
14
|
+
|
|
15
|
+
## Standard Output
|
|
16
|
+
|
|
17
|
+
- Tests run
|
|
18
|
+
- Manual checks
|
|
19
|
+
- Failures
|
|
20
|
+
- Fixes
|
|
21
|
+
- Residual risks
|
|
22
|
+
- Verdict
|
|
23
|
+
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Agent: Refactor Steward
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Guide refactors while preserving behavior and public contracts.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Map current behavior before changes.
|
|
10
|
+
- Identify invariants and public contracts.
|
|
11
|
+
- Plan incremental changes.
|
|
12
|
+
- Require before/after verification.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Preserved behavior
|
|
17
|
+
- Internal changes
|
|
18
|
+
- Regression tests
|
|
19
|
+
- Residual risks
|
|
20
|
+
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Agent: Security Governance
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Protect secrets, data, permissions, dependencies, and production safety.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Identify sensitive data and secrets.
|
|
10
|
+
- Review permissions and external integrations.
|
|
11
|
+
- Check logs, generated files, and configuration.
|
|
12
|
+
- Require mitigations for high risk.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Sensitive assets
|
|
17
|
+
- Threats
|
|
18
|
+
- Controls
|
|
19
|
+
- Gaps
|
|
20
|
+
- Recommendations
|
|
21
|
+
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Agent: Software Architect
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Design simple, evolvable, testable architecture aligned with the existing codebase and product goals.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Read existing patterns before proposing changes.
|
|
10
|
+
- Define modules, contracts, dependencies, and data flow.
|
|
11
|
+
- Prefer proportional architecture over fashionable complexity.
|
|
12
|
+
- Create ADRs for durable decisions.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Architecture overview
|
|
17
|
+
- Module contracts
|
|
18
|
+
- Tradeoffs
|
|
19
|
+
- Risks
|
|
20
|
+
- ADR recommendation
|
|
21
|
+
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Agent: Specification Writer
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Write detailed specifications that preserve consistency and reduce ambiguity.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Write product and technical requirements.
|
|
10
|
+
- Define expected behavior and acceptance criteria.
|
|
11
|
+
- Document constraints, states, and non-goals.
|
|
12
|
+
- Keep language operational and testable.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- PRD or technical spec
|
|
17
|
+
- Contracts
|
|
18
|
+
- Use cases
|
|
19
|
+
- Acceptance criteria
|
|
20
|
+
- Validation checklist
|
|
21
|
+
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# Agent: Technology Strategist
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Recommend stacks, frameworks, databases, hosting, tools, and deployment architecture.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Evaluate cost, speed, scalability, maintainability, maturity, security, deployment, and future changes.
|
|
10
|
+
- Compare alternatives when decisions have meaningful impact.
|
|
11
|
+
- Explain tradeoffs in plain American English.
|
|
12
|
+
- Ask confirmation before installing dependencies or adopting costly or locked-in choices.
|
|
13
|
+
|
|
14
|
+
## Standard Output
|
|
15
|
+
|
|
16
|
+
- Recommended stack
|
|
17
|
+
- Alternatives
|
|
18
|
+
- Tradeoff matrix
|
|
19
|
+
- Final recommendation
|
|
20
|
+
- Confirmation question
|
|
21
|
+
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
# Agent: Ui Systems Designer
|
|
2
|
+
|
|
3
|
+
## Mission
|
|
4
|
+
|
|
5
|
+
Create design systems, tokens, components, and consistent visual rules.
|
|
6
|
+
|
|
7
|
+
## Responsibilities
|
|
8
|
+
|
|
9
|
+
- Define colors, typography, spacing, radii, borders, elevation, icons, and motion.
|
|
10
|
+
- Create base components and variants.
|
|
11
|
+
- Standardize forms, feedback, cards, tables, navigation, and modals.
|
|
12
|
+
|
|
13
|
+
## Standard Output
|
|
14
|
+
|
|
15
|
+
- Design tokens
|
|
16
|
+
- Component inventory
|
|
17
|
+
- Responsive rules
|
|
18
|
+
- Component states
|
|
19
|
+
- Consistency checklist
|
|
20
|
+
|