Skip to content
Skills Library
Programming · Building & coding

backend-implement

/backend-implement

Phase 4 (backend tasks). Implements one PLAN.md task in Python/FastAPI following the layer pattern and edge-case checklist. Use for each unticked backend task after the plan is approved.

Repository
sdlc-kit ↗
Licence
MIT
Last repository change
08.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Phase 4 (backend tasks). Implements one PLAN.md task in Python/FastAPI following the layer pattern and edge-case checklist. Use for each unticked backend task after the plan is approved.

Original author description

Phase 4 (backend tasks). Implements one PLAN.md task in Python/FastAPI following the layer pattern and edge-case checklist. Use for each unticked backend task after the plan is approved.

How it works

  1. Steps
  2. Done when
Original SKILL.md headings · 43 lines, 489 words
SKILL.md preview
---
name: backend-implement
description: Phase 4 (backend tasks). Implements one PLAN.md task in Python/FastAPI following the layer pattern and edge-case checklist. Use for each unticked backend task after the plan is approved.
---
# Backend implement (phase 4, backend tasks)

Do ONE task at a time. Max 3 tasks per chat.

## Steps
1. Read PROGRESS.md and PLAN.md. Pick the next unticked backend task. Confirm the branch:
   `git branch --show-current` must match PROGRESS.md. The task's tests must already be red (PROGRESS.md has
   their red lines); if not, run /write-tests for it first.
2. Open the pattern source files from "Codebase notes". Copy their structure, imports,
   naming, dependency injection and error handling. Do not invent a new style.
3. `wc -l` each file you will edit. If the change would pass 200 lines, do the split first.
4. Write the smallest code that makes this task's tests pass, in layer order: schema → repository → service →
   route. Before using any function, class or setting, confirm it exists: `rg -n "def <name>|class <name>" backend/app`.
   A library API the codebase doesn't use yet: check the installed version (`pyproject.toml` or the lock file)
   and follow that version's docs; can't verify → say so in PROGRESS.md.
5. Edge-case checklist. Handle each one, or write `N/A: <reason>` in the PROGRESS.md log:
   - [ ] New route requires the auth dependency (public only if PLAN.md's API table says so)
   - [ ] `Create`/`Update` schemas have no server-owned fields (`id`, owner id, `role`, `is_admin`, timestamps)
   - [ ] Not found → project's not-found error (404)
   - [ ] Belongs to another user / wrong role → forbidden error (403), checked in the service
   - [ ] Duplicate → catch `IntegrityError` → conflict error (409)
   - [ ] Invalid input → `Field` constraints in the schema (422); max lengths = DB column lengths
   - [ ] Optional/nullable fields handled in service and response
   - [ ] Empty list returns `[]` (+ pagination info), never 404
   - [ ] Pagination: default 20, max 100, stable `order_by`
   - [ ] Multi-write operations in one transaction
   - [ ] No N+1: relations in the response are eager-loaded
   - [ ] UTC datetimes, `Decimal` money
   - [ ] No secrets or personal data in logs or responses
6. Register new routers the same way the pattern source does (find with `rg -n "include_router" backend/app`).
7. Verify on touched files (from `backend/`):
   `ruff check <files> && ruff format <files> && mypy --follow-imports=silent <files>`
   Fix all errors. No `# noqa` / `# type: ignore`.
   Then run this task's tests: all green (mark their Test plan rows ✅). Still red while the code looks right →
   re-check the expected value against REQUIREMENTS.md before changing more code.
8. Tick the task in PLAN.md. Append to PROGRESS.md log: task id, files changed, edge cases N/A with reasons.

## Done when
- [ ] Task ticked, every file ≤ 200 lines
- [ ] ruff and mypy output shown clean in this chat
- [ ] This task's tests shown red before the code and green after
- [ ] Every checklist item handled or marked N/A with a reason

Versions

The database has no other skills named backend-implement.

Database snapshot: 13.11.2026 · package version 22879cb3c141 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100frontend-implement
    Phase 4 (frontend tasks). Implements one PLAN.md task in React + TypeScript + Tailwind + shadcn/ui with the UI-state and edge-case checklist. Use for each unticked frontend task after the plan is approved.
  • 86Backend Python Expert
    当用户需要进行 Python 后端开发时使用。此 Skill 提供 FastAPI 开发、异步编程和性能优化等 Python 后端开发全栈能力支持。
  • 91stack-backend
    Backend conventions for the FastAPI + React stack (app/, Python 3.12, FastAPI, uv, pytest). Use when creating or changing endpoints, services, schemas, tests or Python dependencies.
  • 100init-backend
    Initialize a production-oriented backend project using Node.js with TypeScript, Python with FastAPI and uv, or Go. Use when the user asks to initialize, scaffold, bootstrap, or set up a backend.
  • 96dev-code-backend
    一句话生成项目·后端编码。按设计实现后端(FastAPI/Flask/Express)+数据库。Use when 后端编码/写后端.
  • 100fastapi-router-creator
    Create fastapi router creator operations. Auto-activating skill for Backend Development. Triggers on: fastapi router creator, fastapi router creator Part of the Backend Development skill category. Use when working with APIs or building integrations. Trigger with phrases like…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.