Menu
Full dev pipeline: spec (optional) → build → release → install. Chains all dev skills in sequence with directory guards. Runs from $CAREER_OS_PLUGIN.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use this skill whenever the user asks to implement, build, fix, ship, add, refactor, migrate, or change ANY code — features, bugs, plugins, skills, migrations, hooks, rules, configs, in any repo. Triggers on 'build X', 'fix Y', 'implement Z', 'ship this to <plugin>', a ticket id with code work. This is the Agentic SDLC pipeline; do NOT hand-roll `codex exec` or ad-hoc git/PR shipping — route through Stage 0 (claim), the 9 core stages, the Gate-A.5 change-manifest gate, Gate-A.7 design-review gate, Stage 5.5/5.6/5.7/5.8 quality gates, and Stage 10 (completion).
Activate real-time prompt sharpening and persona detection. Use when the user says "co-dialectic", "cod", "codi on", "improve my prompts", "prompt sharpening", "teach me to prompt", or wants to improve their AI communication skills. Provides status line, persona system, caliber enforcement, prompt improvement, context management, auto-codification protocols, and auto-verification by stakes (Protocol 8 — fires hallucination-detector / judge-panel / unknown-unknown / canonical-claim verifier automatically before every substantive output, scaled to the stakes of the artifact).
Surfaces one-week and two-week follow-up nudges for applications that are applied and awaiting response, with a plain-text draft ready for the human to approve. Draft-only: never sends. Use when the user asks what to follow up on, stale applications, application nudges, or job-search follow-ups.
Detects explicitly shareable career milestones in the job pipeline and surfaces draft-only brand-post prompts. Fail-closed by firewall design: no shareable flag means no suggestion. Use when the user asks for milestone brand moments, career-to-brand prompts, or shareable pipeline milestones.
Career OS home screen and central router. Two jobs: show the dashboard and route every action to the correct skill. Mission Control reads and presents but never directly edits persistence files.
Maps your network to target companies. Discovers warm intro paths, scores connection strength (5-level scale), ingests new contacts from conversation, and recommends who to reach out to and how. Also detects relationship origin (where/when you met) and cohort clusters (people from the same company/era). Records inbound recruiter DMs that came from the user's public posts as brand-attributed pipeline opportunities. Say "who do I know at [Company]", "how do I know [Name]", "tell me about [Contact]", or "a recruiter DM'd me after seeing my post".
| name | CI Pipeline |
| description | Full dev pipeline: spec (optional) → build → release → install. Chains all dev skills in sequence with directory guards. Runs from $CAREER_OS_PLUGIN. |
| triggers | ["ci","ci pipeline","run ci","full pipeline","build and release"] |
Chains the dev skills into a single pipeline: spec → build → release → install. Eliminates the need to remember which skill to run next or which directory to be in.
Always start your response with:
━━━ Career OS: CI Pipeline ━━━
Directory guard (enforced): Before ANY work, run:
bash "$CLAUDE_PLUGIN_ROOT/dev/guard.sh" plugin "CI Pipeline"
If it exits non-zero, STOP. Show the guard's output and do nothing else.
--from-spec)Read work orders from $CAREER_SPECS/work-orders/ (read-only cross-directory access).
$CAREER_SPECS/PRD.md — extract planned skills from Skill Inventory$CAREER_SPECS/work-orders/skills/If all features are already specced, skip to Stage 1.
This stage follows the spec-feature SKILL.md spec — read it for details.
Read work orders and implement features.
$CAREER_SPECS/work-orders/skills/━━━ CI: Build Plan ━━━
Work orders ready to build:
1. WO-019 apply-tracker — post-application lifecycle tracking
2. WO-021 job-match-scorer — 6-category match scoring engine
Already implemented: 13 skills
Nothing to build: 9 work orders (meta/infra tasks)
Proceed? (y/n)
skills/{name}/SKILL.mdbash tests/test-hooks.sh after each featureIf all work orders are already built, skip to Stage 2.
This stage follows the build-feature SKILL.md spec — read it for details.
Version bump, test, commit, push.
bash tests/test-hooks.sh — full suite must pass.claude-plugin/plugin.json for current versiongit log since last release to classify changesplugin.jsonmigrations/v{old}-to-v{new}.shCLAUDE.md version lineThis stage follows the release-plugin SKILL.md spec — read it for details.
Refresh the local Claude Code plugin cache.
claude plugin list for current installed versionclaude plugin update career-intelligence@xos or uninstall + reinstallclaude plugin list shows new versionThis stage follows the install-plugin SKILL.md spec — read it for details.
[--from-spec]
│
▼
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ Spec │───▶│ Build │───▶│ Release │───▶│ Install │
│ (opt.) │ │ │ │ │ │ │
│ $SPECS │ │ $PLUGIN │ │ $PLUGIN │ │ $PLUGIN │
│ read │ │ write │ │ commit │ │ refresh │
└─────────┘ └─────────┘ └─────────┘ └─────────┘
│ │
▼ ▼
tests must tests must
pass here pass here
With --dry-run, show what each stage would do without executing:
━━━ CI: Dry Run ━━━
Stage 0 (Spec): skipped — not requested
Stage 1 (Build): 0 features to build (all implemented)
Stage 2 (Release): would bump 0.9.0 → 0.10.0 (2 skills updated)
Stage 3 (Install): would refresh plugin cache (current: 0.9.0)
Run "ci" to execute.
After pipeline completes (or stops on failure), show summary:
━━━ CI Pipeline Complete ━━━
| Stage | Status | Detail |
|-------|--------|--------|
| Spec | skipped | not requested |
| Build | skipped | all work orders implemented |
| Release | done | v0.9.0 → v0.10.0, 163 tests pass |
| Install | done | plugin cache refreshed |
Total time: {duration}