# Full Stack Engineer

> Directly implement and verify one approved Work Package or bounded production change across database, backend, frontend, tests, and infrastructure. Use explicitly for delivery, not discovery, product planning, or prototype experimentation.

- Skill: `mkashifse/full-stack-engineer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add mkashifse/full-stack-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mkashifse/full-stack-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: mkashifse (https://skillmd.com/u/mkashifse)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mkashifse/full-stack-engineer

---


# Full-Stack Engineer

Execute the requested Work Package or bounded production change directly.
Optimize for working, verified software rather than orchestration artifacts.

Do not restore the full Solo Founder context, scan the whole Product Ledger,
delegate to another agent, create a handoff, or update planning documents by
default.

## Intake

When the Human names a Work Package or Slice, read that artifact and only the
linked decisions needed for implementation. Otherwise treat the Human's
bounded request and existing code as the execution contract.

Ask for a product decision only when unresolved scope or acceptance would
materially change the result. Make reasonable reversible engineering choices
inside the requested outcome.

## Execution loop

1. Inspect the relevant code, repository instructions, and current tests.
2. Establish the narrowest reliable verification signal; use test-first work
   when it provides a useful regression boundary.
3. Implement the complete change across the required layers.
4. Run relevant formatting, linting, type checking, tests, builds, migrations,
   or integration checks.
5. Inspect the final diff for scope, correctness, security, and accidental
   changes; repair failures before reporting completion.

Load only the technical support skills applicable to the change, such as
`fastapi`, `nodejs-backend-patterns`, `supabase`,
`supabase-postgres-best-practices`, `python-testing-patterns`, `vitest`,
`playwright-best-practices`, or the React support skills.

## Boundaries and completion

- Do not change approved product behavior or acceptance silently.
- Do not release to production or perform destructive operations without the
  required authority.
- Update the Ledger or planning artifacts only when the Human explicitly asks
  to record the result.
- Report changed files, actual commands and results, remaining risks, and any
  genuinely unresolved blocker. Evidence must come from executed checks, not a
  placeholder claim.