一键导入
persisting-agent-outputs
Protocol for agents to write structured outputs that survive session resets and are findable by the orchestrator.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Protocol for agents to write structured outputs that survive session resets and are findable by the orchestrator.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | persisting-agent-outputs |
| description | Protocol for agents to write structured outputs that survive session resets and are findable by the orchestrator. |
| type | orchestrate |
| tier | core |
| trigger | save output, persist results, write report, store findings, agent output location |
Agent outputs must be findable after session reset. The orchestrator reads these to resume work and make decisions. This skill defines the exact write protocol.
All agent outputs go to:
.jonggrang/.output/features/{feature_id}/{phase}-{role}-output.json
Examples:
.jonggrang/.output/features/auth-feature-abc123/
07-lead-architecture-plan.json
08-developer-task-001.json
09-reviewer-design-check.json
11-reviewer-code-quality.json
12-test-lead-test-plan.json
13-tester-results.json
Every output file must include this header:
{
"jonggrang-output": true,
"feature_id": "auth-feature-abc123",
"phase": 8,
"role": "developer",
"task_id": "task-001",
"agent_id": "developer-auth-001",
"timestamp": "2024-01-01T00:00:00Z",
"status": "completed",
"output": {
// role-specific payload here
}
}
Lead (architecture plan):
{
"output": {
"work_type": "MEDIUM",
"tasks": [
{ "id": "task-001", "title": "...", "description": "...", "files": [...], "blocked_by": [] },
{ "id": "task-002", "title": "...", "description": "...", "files": [...], "blocked_by": ["task-001"] }
],
"tech_decisions": [...],
"risk_factors": [...]
}
}
Developer (implementation):
{
"output": {
"task_id": "task-001",
"files_modified": ["src/auth.ts"],
"files_created": ["src/auth.test.ts"],
"summary": "Implemented JWT auth with refresh tokens",
"notes": "Used bcrypt for password hashing"
}
}
Reviewer (review report):
{
"output": {
"approved": true,
"score": 8,
"violations": [],
"warnings": ["Consider adding rate limiting"],
"required_fixes": []
}
}
Tester (test results):
{
"output": {
"tests_passed": true,
"total": 24,
"passed": 24,
"failed": 0,
"coverage": 87.3,
"failed_tests": []
}
}
When an agent needs to find a previous phase's output:
.jonggrang/.output/features/{feature_id}/{phase}-{role}-*.jsonThe orchestrator knows the feature_id from MANIFEST.yaml:
feature_id: auth-feature-abc123
Mayar API & CLI integration skill. - APP INTEGRATION: Use `mayar docs <topic>` to read REST API specs (endpoints, schemas), then write native HTTP requests (fetch/axios) in user app code. Do NOT run CLI inside backend scripts. - DIRECT SHELL / ADMIN TASKS: Use Mayar CLI commands directly (`mayar invoice list`, `mayar balance`, `mayar product create`, `mayar status`, etc.) for direct operational and testing tasks in terminal. Targets Mayar API v2. Node.js 18+.
16-phase feature orchestration workflow. Runs in the main thread as Kernel Mode. Coordinates the Lead→Developer→Reviewer→TestLead→Tester assembly line.