メニュー
Implementation-agent delegation contract for FRIDAY. Load when FRIDAY delegates to temper-backend, temper-frontend, temper-tester, temper-devops, or another implementation agent, including task-driven, direct-action, bugfix, and recovery turns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structure and rules for .NET projects using Clean Architecture with DDD. Use when the project has complex business domain, multiple use cases, need to test business logic in isolation, or when the system is enterprise, e-commerce, ERP, CRM, or any rich domain. Do not use for simple CRUDs without logic — prefer Vertical Slice in that case. For implementation details, load the required `backend/dotnet/orms/ef-core/*/SKILL.md` leaf skill(s) or your chosen data access skill.
Structure and rules for .NET projects using Hexagonal Architecture (Ports & Adapters). Use when the project has multiple input channels (API, CLI, message queue), need to test the domain in isolation, or when adapters change frequently. Do not use for simple CRUDs without logic — prefer Vertical Slice in that case. For implementation details, load the required `backend/dotnet/orms/ef-core/*/SKILL.md` leaf skill(s) or your chosen data access skill.
Structure and rules for .NET projects using Onion Architecture. Use when the project has a strong domain-centric focus with DDD, aggregate roots, and the Specification pattern. All dependencies point inward toward the domain core. Do not use for simple CRUDs without logic — prefer Vertical Slice in that case. For implementation details, load the required `backend/dotnet/orms/ef-core/*/SKILL.md` leaf skill(s) or your chosen data access skill.
Canonical DbContext setup and registration rules for EF Core. Load when creating or modifying DbContext classes or their DI wiring.
Pure LINQ standards for .NET 10 projects. Covers language operators, query composition, projection patterns, filtering, grouping, and performance best practices over IEnumerable<T> and IQueryable<T>. Load when writing or reviewing LINQ expressions in any layer. DO NOT load expecting EF Core-specific methods (ToListAsync, AsNoTracking, Include, ExecuteUpdateAsync) — those belong to `backend/dotnet/orms/ef-core/query-best-practices/SKILL.md`.
Canonical rules for using AppDbContext DIRECTLY from application code (use cases / handlers) when the project's data-access pattern is Direct DbContext — no repositories, no UnitOfWork. Load when the chosen pattern is Direct DbContext and a use case reads or writes data. This is the counterpart to repository-usage; never load both for the same task.
| name | friday-implementation-delegation |
| description | Implementation-agent delegation contract for FRIDAY. Load when FRIDAY delegates to temper-backend, temper-frontend, temper-tester, temper-devops, or another implementation agent, including task-driven, direct-action, bugfix, and recovery turns. |
This skill defines the execution-agent delegation contract for FRIDAY.
When loaded, it is authoritative for:
Use this skill when FRIDAY delegates to temper-backend, temper-frontend, temper-tester, temper-devops, or another implementation agent.
workflow/friday/state-schema remains authoritative for universal delegation prohibitions.
For normal task-driven implementation, the prompt must contain only:
Implement task T001: Add Product to Inventory (user-story US-001, Backend)
That is the whole prompt.
FRIDAY must not add:
The implementation agent resolves its task metadata from Plan/INDEX.md, reads the task file at Location, reads the parent work item source file, and loads its own skills.
When there is no task file and the user asks for a direct bugfix, delegate in plain domain language:
Fix bug: Order total calculates incorrectly when discount applies.
Affected area: Order total calculation.
Expected behavior: Discounted orders show correct total after tax.
Rules:
Affected area: only when the user provided it or it is necessary to avoid ambiguity.When backend implementation is approved without task artifacts, delegate in plain domain language and state the mode explicitly:
Approved direct action: Implement backend change for order discount validation.
Affected area: Discount validation during order updates.
Expected behavior: Invalid discounts are rejected and valid discounts are preserved.
Constraints: No task file or Plan artifacts exist for this request.
Rules:
Affected area: only when it helps disambiguate scope.Constraints: only when FRIDAY must preserve the no-task direct-action boundary or another user-approved limit.When an implementation agent failed after creating partial work, re-delegate with the minimum continuation context:
Task: Implement task T003: Add Order Status Validation (user-story US-002, Backend)
Error: Agent ran out of context before completing the handler.
Existing work: Status enum updated, validator created, interface created.
Instruction: Continue from where the previous attempt stopped. Do not regenerate completed work. Finish the remaining scope.
Rules:
If output is unusable because FRIDAY's original prompt missed necessary clarification, re-delegate with only that missing clarification added.
Task: [original task]
Clarification: [exact missing context]
Instruction: Complete the task using this clarification.
Do not resend large restated context if one missing clarification is enough.
Implement task [T###]: [title] ([work item type] [work item id], [category]).Approved direct action: and stays in plain behavioral language.If any check fails, rewrite to the smallest prompt that preserves the missing information.
This skill is not for analyst or architect loops.
For those agents, load their dedicated Friday workflow contracts:
workflow/friday/analyst-communication.workflow/friday/architect-communication.