professional-development
Plan and track professional development by turning career-direction priorities into sequenced capability, credential, course, and resource decisions with current progress and next actions. Use for learning or credential planning tied to a career direction; do not use for general career discovery, evaluating one job, ordinary interview preparation, or resume rewriting.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- professional-development
- description
- Plan and track professional development by turning career-direction priorities into sequenced capability, credential, course, and resource decisions with current progress and next actions. Use for learning or credential planning tied to a career direction; do not use for general career discovery, evaluating one job, ordinary interview preparation, or resume rewriting.
02 资源文件 3
- 参考文档agents/openai.yaml327 B
- 资产文件assets/icon-large.svg3.1 KB
- 资产文件assets/icon-small.svg1.3 KB
03 SKILL.md 正文
Professional Development
Turn strategic career priorities into practical development work and keep its current state coherent.
Boundaries
career-directionowns reusable career goals, constraints, positioning, target roles, hypotheses, and high-level development priorities: what matters and why.- This skill owns the execution layer: capability gaps, development goals, credentials, courses and other resources, prioritization, sequencing, progress, completed evidence, dependencies, review dates, and next actions: what the user is doing about it.
- Do not own general career discovery, specific-opportunity fit, ordinary interview preparation, or resume/profile production.
- Do not duplicate
teach-mepedagogy. Career Coach selects and tracks the development objective; an optional teaching or practice capability may design or run learning when the user has a genuine learning goal.
Workflow
- Follow shared source discovery and authority. Retrieve only the current Career Direction priority and constraints needed for the plan and relevant current development entries. A supplied priority can support a task-only plan; resolve the existing development authority before any persistent update. Read preferences and storage when planning/output defaults, a new-record destination, or an authorized settings change matters. Retrieve history only under the shared conditions.
- Translate confirmed strategic priorities into actionable development goals. Give each goal a stable
PD-...identifier and distinguish capability acquisition from credential acquisition. - Compare capability gaps and candidate investments by career relevance, urgency, expected evidence, effort, cost, prerequisites, portability, and fit with the user's constraints. Preserve unknowns rather than inventing outcomes.
- Choose a proportionate development approach and sequence. Keep courses, practice, projects, mentoring, credentials, and other resources as options rather than assuming a course or credential is required.
- When durable tracking is authorized, record or update current progress, completed evidence, dependencies, target or review dates, provenance, and the smallest useful next action in the canonical professional-development record under its shared procedure. Require explicit user confirmation before persisting an inferred goal or committing consequential cost, time, or credential activity.
- Reassess priorities when new evidence, changed direction, completed work, or a blocked dependency changes the plan. Route durable changes to reusable strategic priorities back to
career-direction; keep detailed execution here.
Supporting capabilities
- When available, use
research-briefingonly when current external facts materially affect a credential, course, labor-market, employer, industry, or geographic decision. If it is unavailable, label affected claims unverified or unknown. Keep sourced facts separate from Career Coach judgments and user preferences. - When available, use
teach-meonly when the user has a genuine learning or practice objective. Do not invoke it merely to make a roadmap, choose a resource, or record progress; if it is unavailable, continue locally and do not imply a handoff occurred. - When available, use
remember-meonly for narrow stable personal context that is not owned by Career Coach and materially affects the plan. If it is unavailable, continue with neutral defaults. - Continue locally when an optional capability is unavailable; never imply that an unavailable handoff occurred.
References
- Read professional-development record management before creating, updating, or auditing the current development record.
- Read persistent-record lifecycle and audits when a lifecycle trigger is due or structural maintenance is proposed.
- Read career-direction record management when resolving Career Direction identity, history, or a bounded strategic-priority update.
Output
Match depth to the request. Distinguish confirmed current state, user goals, supported gaps, candidate investments, unknowns, completed evidence, and proposed next actions. A plan is not proof of capability, experience, or credential completion.
04 同仓库更多 Skills
personal-shopper
Compare products, services, contractors, and project costs against the user's needs, scope, qualifications, fit, and current regional evidence; research official permit fees and supported reference-class forecasts; build package-aware groceries from finalized delegated meal plans. Use for direct product shopping, named-option alternatives, hardware specifications, service quotes, project estimates, shopping preferences, or delegated grocery work; do not choose or redesign recipes.
superb-skills
Design and evaluate reusable instructions, skills, plugins, contracts, and tests; advise on benchmark design and results. Use for instruction reliability or benchmark critique, explanation, and design. Skip one-off rewrites and ordinary use of fixed instructions.
coding-preferences
Apply relevant portable coding preferences to implementation, code review, explanation, and engineering prose. Use when reusable coding conventions could affect the result; do not use to manage general personal or writing preferences.
code-quality-review
Review code for correctness and material maintenance risks when requested or accepted; ordinary implementation and coding-preference work do not acquire a reviewer prerequisite.
fixture-simple-normalizer
Fixture target for one deterministic filename normalization.
fixture-preference-planner
Fixture target for testing preference intake, editable project settings, task overrides, and verified operational lessons.