Grace
Read root and nearest AGENTS.md before editing. For non-trivial tracked work, use the repository's docs/Development process.md and installed dev-process. Current source and live tracker evidence determine implementation facts.
Load the relevant context
| Task |
Reference |
| Repository layout and project boundaries |
Project map |
| Tracker, branch, review, validation, or cleanup |
Workflow |
| Specification and readiness |
Specification profile, with installed specification |
| DTOs, events, parameters, serializers, shared code |
Shared contracts |
| HTTP, SDK, CLI, authorization at public entrypoints |
Public surfaces |
| Orleans, event sourcing, replay, durable transitions |
Actors and durability |
| RBAC, PATs, OIDC, TestAuth, path permissions |
Security |
| Uploads, manifests, ContentBlocks, Service Bus, Aspire |
Runtime and storage |
| Selecting or changing tests |
Tests |
| Contributor, product, or workflow documentation |
Docs |
Load only the references needed for the current slice. The installed specification owns feature lifecycle and traceability; design-readiness resolves open product/domain/architecture choices; dev-process owns delivery. Avoid repeating their full checklists here.
Grace-specific defaults
Grace uses Product V1 unless the owner chooses another profile. It has no production legacy data; add compatibility or migration behavior only for a requirement that actually exists.
Prefer a vertical slice through the nearest stable public boundary. Propagate a changed public or durable contract through the relevant Types, Shared, Server, Actors, SDK, CLI, generated artifacts, docs, and tests. Preserve established Grace vocabulary.
Use focused local evidence and required GitHub Validate on the final PR revision. Local Fast is optional broad preflight; Full is for integration reproduction or diagnosis. The repository owns current commands and project membership.
Planning-only requests remain planning. Tracker setup and implementation follow the user's requested scope. Use PowerShell and Markdown skills for generated scripts and documents, with PowerShell examples before bash / zsh where applicable. Explain unresolved product decisions through concrete user behavior.
1---2name: grace3description: Route Grace repository work to current workflow, domain, contract, runtime, testing, and documentation guidance.4---56# Grace78Read root and nearest AGENTS.md before editing. For non-trivial tracked work, use the repository's docs/Development process.md and installed `dev-process`. Current source and live tracker evidence determine implementation facts.910## Load the relevant context1112| Task | Reference |13| --- | --- |14| Repository layout and project boundaries | [Project map](references/project-map.md) |15| Tracker, branch, review, validation, or cleanup | [Workflow](references/workflow.md) |16| Specification and readiness | [Specification profile](references/specification-profile.md), with installed specification |17| DTOs, events, parameters, serializers, shared code | [Shared contracts](references/contracts-and-shared.md) |18| HTTP, SDK, CLI, authorization at public entrypoints | [Public surfaces](references/public-surfaces.md) |19| Orleans, event sourcing, replay, durable transitions | [Actors and durability](references/actors-and-durability.md) |20| RBAC, PATs, OIDC, TestAuth, path permissions | [Security](references/security-and-auth.md) |21| Uploads, manifests, ContentBlocks, Service Bus, Aspire | [Runtime and storage](references/runtime-and-storage.md) |22| Selecting or changing tests | [Tests](references/tests.md) |23| Contributor, product, or workflow documentation | [Docs](references/docs-and-contributing.md) |2425Load only the references needed for the current slice. The installed `specification` owns feature lifecycle and traceability; `design-readiness` resolves open product/domain/architecture choices; `dev-process` owns delivery. Avoid repeating their full checklists here.2627## Grace-specific defaults2829Grace uses Product V1 unless the owner chooses another profile. It has no production legacy data; add compatibility or migration behavior only for a requirement that actually exists.3031Prefer a vertical slice through the nearest stable public boundary. Propagate a changed public or durable contract through the relevant Types, Shared, Server, Actors, SDK, CLI, generated artifacts, docs, and tests. Preserve established Grace vocabulary.3233Use focused local evidence and required GitHub Validate on the final PR revision. Local Fast is optional broad preflight; Full is for integration reproduction or diagnosis. The repository owns current commands and project membership.3435Planning-only requests remain planning. Tracker setup and implementation follow the user's requested scope. Use PowerShell and Markdown skills for generated scripts and documents, with PowerShell examples before bash / zsh where applicable. Explain unresolved product decisions through concrete user behavior.
scottarbeit