OpenKnowledgeBank
Bundle catalog

roles bundle

Full-Stack Developer

A free, open-source set of 10 Markdown files that gives an AI assistant practical guidance for the Full-Stack Developer role.

Use this bundle to plan and review Full-Stack Developer work with evidence, assumptions, owners, and review points made explicit. The page previews a role guide, an overview, a workflow, and a template; the intended output is full-stack delivery brief. Start source review with O*NET OnLine — Summary / 15 1254.00.

Project-reviewed beta
Preview contents Download bundle Inspect source

10 Markdown files · 1,370 words · no signup · CC-BY-4.0

Inspect before downloading

See what is inside

These previews come from the published bundle files, so you can judge the method and writing before using it.

Role guide

Full-Stack Developer source-backed Guide

Defines source-backed full-stack software delivery, evidence handling, and action boundaries.

Read the file

Overview

Full-Stack Developer overview

Use this bundle to prepare source-backed full-stack software delivery analysis and a review-ready full-stack delivery brief.

Read the file

Workflow

Full-Stack Developer source-backed triage

1. State the requested decision or artifact. 2. Inventory evidence: requirements and acceptance criteria; frontend, backend, runtime, repository, and environment versions; API, schema.

Read the file

Template

full-stack delivery brief

Review-ready artifact for full-stack software delivery, evidence quality, verification, and controlled next actions.

Read the file

Is this bundle right for your task?

Who it is for

  • People performing or supporting Full-Stack Developer work, plus teams reviewing its decisions and outputs
  • Teams working in Software engineering, Technology

When to use it

  • A Full-Stack Developer task needs a structured plan, evidence checklist, or review-ready output.
  • A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.

What you need to provide

  • The task objective, intended audience, working context, constraints, source material, and decision owner.
  • Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.

Tasks and expected outputs

Questions it helps answer

  • Prepare a full-stack delivery brief without fabricating local facts.
  • Separate verified, provided, assumed, and missing evidence.
  • Produce a review-ready recommendation with explicit verification and approval boundaries.

What it helps produce

  • full-stack delivery brief

Practical example

Use it with an agent

Load the bundle as context, provide the evidence named above, then adapt this example to your situation.

Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Full-Stack Developer work by producing full-stack delivery brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1254.00, then confirm that the reference is current and applicable. Inspect Full-Stack Developer source-backed Guide before drafting.

Context path: bundles/roles/full-stack-developer

What the bundle includes

Frameworks

  • source-evidence matrix
  • full-stack software delivery review matrix
  • qualified-review gate

Evaluations

  • Full-Stack Developer source verification check

Sources used to build this bundle

These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.

O*NET OnLine — Summary / 15 1254.00 Role or occupation reference for Full-Stack Developer scope and source checks. W3C — Standards Guidelines / Wcag Practice or subject-matter reference for Full-Stack Developer methods, constraints, and source checks.

Limitations and safe use

Do not use this for

  • Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.

Known limitations

  • Use the cited official, originator, standards, or professional sources for general full-stack software delivery context; local facts, records, values, states, and permissions require inspected evidence.
  • Task-specific work requires current evidence for requirements and acceptance criteria; frontend, backend, runtime, repository, and environment versions; API, schema, state, and integration contracts; authentication, authorization, privacy, and threat evidence; tests, accessibility, performance, observability, deployment, and rollback evidence.
  • Do not infer interface behavior, authorization, data compatibility, accessibility, test result, performance, or production state.

Safety notes

  • Minimize personal, customer, employee, financial, credential, security, privileged, and other sensitive data.
  • Require explicit confirmation before deploying code, changing schemas or access, handling secrets, or modifying production.
  • Route legal, privacy, security, compliance, financial, employment, safety, and other qualified judgments to an evidenced accountable reviewer.

Next step

Inspect it before relying on it

Download the bundle for use, review its source files and evidence, or read the agent guidance. If the project is useful, starring the repository helps others discover it.

Download Review source Agent guidance Star on GitHub