Development Workflow
You need to develop strictly in a contract-first manner. For example,
,
should be placed in the
directory.
Prioritize Using SKILL
When you are unsure, prioritize retrieving knowledge from existing SKILLs. Use SKILLs whenever available.
Documentation Standards
Use a unified standard format for writing documents, e.g., <SKILL: z-document>.
Read Product Documents
Before each development task, you need to specify a product document. By default, you can use the
or
tool to list the latest documents from the
directory, and let the user select or input
.
Development Workflow
Create feature branch -> Write technical proposal -> Update Contract -> Create development branch -> Implement code[1] -> Orchestrate services -> Cover API tests -> Cover E2E tests.
[1] The code implementation part involves parallel subagent calls.
Create a
for this workflow.
Loading Specifications
Before writing code, if the corresponding directory's AGENTS.md is not loaded in the context, load it.
Example: When modifying
, load
Every time you write code, you need to load
docs/engineering/common-rules.md
Create Feature Branch
After specifying the product document to be developed, create a remote development branch
with the name
, where
is a summary of the product document content.
Write Technical Proposal
USE FOR: write proposal, update proposal
REFERENCE: [[dev/dev-proposal-template.md]]
Update Contract
USE FOR: write contract, update contract
REFERENCE: [[dev/update-contract.md]]
Implement Code
USE FOR: implemention, write code, coding
REFERENCE: [[dev/write-implementation.md]]
Orchestrate Services
By default, use <SKILL: z-aspire-orchestrator>. If it is not available, use docker-compose + local startup for orchestration.
Write Integrated API Tests & E2E Tests
By default, use <SKILL: z-test>. If it is not available, decide on your own how to cover the tests.