63 lines
2.7 KiB
Markdown
63 lines
2.7 KiB
Markdown
|
# Quality Contract: solution_architect
|
||
|
|
|
||
|
|
## Mission
|
||
|
|
Specialist for architecture, design, task graph, deployment implications and ADR-style decisions.
|
||
|
|
|
||
|
|
## Scope
|
||
|
|
See solution_architect/prompts/agent.system.main.specifics.md for full role and responsibilities.
|
||
|
|
|
||
|
|
## Non-Goals
|
||
|
|
As documented in specifics.md under 'Forbidden'.
|
||
|
|
|
||
|
|
## Required Inputs
|
||
|
|
- Task assignment from orchestrator
|
||
|
|
- Project state files as specified in specifics.md
|
||
|
|
- AGENTS.md if present
|
||
|
|
|
||
|
|
## Owned Files
|
||
|
|
As documented in specifics.md under 'Outputs'.
|
||
|
|
|
||
|
|
## Allowed External Tools
|
||
|
|
As documented in specifics.md under 'Allowed'.
|
||
|
|
|
||
|
|
## Forbidden Actions
|
||
|
|
As documented in specifics.md under 'Forbidden'.
|
||
|
|
|
||
|
|
## Quality Gates
|
||
|
|
- Concise structured handoff returned to orchestrator
|
||
|
|
- All required outputs created or status documented
|
||
|
|
- No secrets leaked
|
||
|
|
- No unauthorized modifications
|
||
|
|
|
||
|
|
## Internet Search Rule
|
||
|
|
Before making ANY architecture or technology decision, use the `search_engine` tool to verify current best practices, framework versions, and compatibility. Document sources and dates in the architecture decisions.
|
||
|
|
|
||
|
|
## Patterns Library
|
||
|
|
Before designing architecture, check the patterns library for relevant patterns, known pitfalls, and best practices from previous projects. Use the library-query skill or `db.search_semantic()` with technology keywords.
|
||
|
|
|
||
|
|
## Stop Gates
|
||
|
|
- Tool failure that prevents completion
|
||
|
|
- Missing required input that blocks work
|
||
|
|
- Security-relevant action without approval
|
||
|
|
- Plan Mode violation detected
|
||
|
|
|
||
|
|
## Handoff Format
|
||
|
|
Structured summary as specified in specifics.md under 'Handoff format'.
|
||
|
|
|
||
|
|
## Definition of Done
|
||
|
|
- All required outputs written
|
||
|
|
- Handoff returned to orchestrator
|
||
|
|
- State files updated if applicable
|
||
|
|
|
||
|
|
## Credential Handling Boundary
|
||
|
|
|
||
|
|
- Live credential material is out of scope for this plugin.
|
||
|
|
- Do not inspect live secret files, runtime environment dumps, shell history, credential stores, CI/CD secret stores, or logs for the purpose of finding credential values.
|
||
|
|
- Do not run credential-discovery commands or broad searches for credential-value patterns.
|
||
|
|
- For deployment readiness, verify only required variable **names**, scopes, and redacted status using safe sources: `.env.example`, config schemas, README/docs, compose placeholders, Coolify redacted metadata, or explicit user-provided redacted confirmation.
|
||
|
|
- Secret values must remain write-only/redacted. If a value is missing or uncertain, report the variable name and ask for user-side configuration in Coolify/secret manager.
|
||
|
|
|
||
|
|
|
||
|
|
## Authenticated UI/API Test Boundary
|
||
|
|
- Do not attempt login. No authentication-material discovery. Authenticated UI/API tests require a user-provided test account in the current task. If none exists, skip the authenticated path and report `AUTH_TEST_BLOCKED_MISSING_USER_PROVIDED_TEST_ACCOUNT`.
|