Gather self-review evidence through a guided competency skill
Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.
The problem
Employees preparing a self-review need concrete evidence of their work rather than relying on memory or a blank competency template.
Agent job
Turn the competency spreadsheet into a role-aware interview, use completed Jira work as prompts and export the employee's evidence.
Expected output
A reviewable evidence collection and development report for the employee's self-review.
Where this framing comes from
Core problem: Editorial purpose framing
Agent job: Editorial purpose framing
Expected output: Editorial purpose framing
Relevant job roles: Editorial purpose framing
Benefit type: Editorial purpose framing
Editorial framing and outcome limits
Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.
Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.
Case-specific decision guidance · untested
Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.
An employee preparing a self-review may remember recent work but overlook earlier contributions or struggle to connect examples with a competency framework. Completed tickets can prompt recall, yet their status alone says little about individual impact.
This job could guide the employee through evidence collection and keep their own explanations visible. A reviewable export supports a grounded self-assessment without turning activity counts into performance judgments or inventing accomplishments.
Why an agent / simpler alternative
Useful judgment
Connect job-relevant competencies with work examples and ask clarifying questions about contribution, outcome and uncertainty.
Simpler alternative
Use a competency worksheet manually when the employee already has a well-organized evidence list.
Unsuitable when
The process evaluates employees automatically or infers sensitive traits and personal characteristics from work records.
Proposed inputs
Name
Competency framework
Owner
Employee or authorized HR owner
Minimum scope
Relevant role/level criteria
Quality check
Clarify ambiguous expectations without inventing standards
Name
Approved work examples
Owner
Employee
Minimum scope
Selected completed tickets and personal context
Quality check
Separate individual contribution from team results
Access and setup — proposed or unknown
Proposed minimum
Use supplied framework excerpts and fictional tickets first; no broad employee analytics or live Jira access.
Compatibility unknowns
Current issue access, role mapping, export tools and exact runtime compatibility are unknown.
External actions requiring approval
Reading additional personnel records, sharing the review or writing into HR systems requires explicit authorization.
Expected deliverable and review checks
Proposed artifact
Employee-owned evidence draft with competency links, contribution statements and development questions.
Critical checks
Trace claims to examples; preserve employee corrections; distinguish completed work, observed outcome and inferred impact.
Missing output evidence
This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.
Failure signals and proposed responses
Signal
A closed ticket becomes proof of success
Why it matters
Completion status hides outcome uncertainty
Proposed response
Ask what changed and retain unknown results.
Signal
Team output is attributed entirely to one person
Why it matters
The draft overclaims contribution
Proposed response
Record the employee's specific role and collaborators fairly.
Effort and cost — unknown
Setup work
Agree role scope and interview/evidence labels.
Ongoing review
Employee verifies every exported claim and chooses what to share.
Unknowns
Record completeness, interview effort, confidentiality review and service costs are unknown.
First check — proposed, unexecuted
Status
proposed_unexecuted
Synthetic fixture
Invent two competencies and three tickets, including a team project and a closed task with unknown outcome; propose interview questions.
Acceptance checks
Ask for evidence rather than inventing impact; separate contribution; produce no rating or HR-system write.
Stop conditions
Stop if evaluation criteria require sensitive inference or the employee cannot verify a claim.
Limits
An evidence collection does not determine performance ratings, promotion eligibility or the truth of self-reported outcomes.
Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Claude CoworkIndependent testing: No
Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.
Minimize Canadian employee records; use consented job evidence and qualified manager review.
Recommended approval boundaries
Review source references and artifacts; approve any posting, external send, ledger entry, contract acceptance or sensitive-data disclosure separately.
More examples of this task
Source-backed approaches using this or another agent. Not independently tested.
Claude Cowork
Build a controlled performance-review workflow
Read the organization’s competency framework, rating definitions and template, then write a reusable skill guiding managers through consistent review drafts.
Official recipe · Publication date unknown · Independently tested: No