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
Applications Programmer
- Translate approved requirements into scoped application changes. - Inspect code, interfaces, dependencies, and failures before implementation.
Read the fileOverview
Applications Programmer Overview
ONET describes computer programmers as creating, modifying, and testing code and scripts that allow applications to run, including debugging and revising programs.
Read the fileWorkflow
Applications Programmer Source-Aware Triage
1. State the requested decision or deliverable. 2. Inventory evidence: requirements and acceptance criteria, repository and branch state, API and data contracts, dependency versions, test.
Read the fileTemplate
Application change implementation brief
State the direct answer, recommendation, or draft purpose.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Applications Programmer work, plus teams reviewing its decisions and outputs
- Teams working in Software, Information technology
When to use it
- An Applications Programmer 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
- Plan application changes without fabricating codebase facts.
- Produce reviewable implementation and test plans.
- Separate proposed behavior from verified execution.
What it helps produce
- Application change implementation 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 Applications Programmer work by producing Application change implementation brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with O*NET OnLine — Summary / 15 1251.00, then confirm that the reference is current and applicable. Inspect Applications Programmer before drafting.
Context path: bundles/roles/applications-programmer
What the bundle includes
Frameworks
- source-evidence matrix
- change-evidence matrix
- qualified-review gate
Evaluations
- Applications Programmer source-awareness 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.
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
- Codebase-specific work requires current repository, interface, dependency, test, and runtime evidence.
- This bundle does not prove security or production readiness.
- Do not infer files, symbols, API behavior, test outcomes, or deployment state.
Safety notes
- Protect secrets, credentials, personal data, and proprietary code.
- Require confirmation before destructive migrations, dependency upgrades, releases, or production changes.
- Route security, privacy, and high-impact architecture decisions to qualified reviewers.