Results for “job-description-parsing”

Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.

Guides the design and structuring of workflow-based Claude Code skills with multi-step phases, decision trees, subagent delegation, and progressive disclosure.

Turns messy business process descriptions into structured workflows, classifies each step for automation potential using a GREEN/YELLOW/RED framework, and produces a prioritized automation roadmap with time savings estimates.

Task Decomposition

Configure and manage - Parse email parser operations. Auto-activating skill for Business Automation. Triggers on: email parser, email parser Part of the Business Automation skill category. Use when working with email parser functionality. Trigger with phrases like "email parser", "email parser", "email".

Decompose work into small, verifiable tasks with explicit acceptance criteria, ordered by dependencies and sliced vertically for reliable implementation.

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).

Tracks asynchronous and multi-step work by creating, listing, viewing, completing, editing, and deleting tasks stored as JSON files in a .dex directory.

Short clarifying interview before starting non-trivial engineering work — surfaces the actual requirement, what's explicitly out of scope, and what proves it's done. Use before writing code when the task's requirement, scope, or definition of done isn't already unambiguous. Not for trivial or fully-specified changes — that's ceremony, not clarity.

Decompose tasks into structured, outcome-defined process entries with complexity triage. Load when user says "decompose this", "break this down", "what steps do I need", "plan this out", "what's the process for", "how do I approach this", or when any complex task needs structured execution planning. Includes a problem-understanding pass before complexity triage. Routes to `problem-to-plan` when the user needs planning deliverables (spec + plan + TODO). Does NOT replace brainstorming — brainstorming is design approval (upstream), this is execution planning (downstream).

Tracks async and multi-step work as JSON tasks in .dex/tasks/, with commands to create, list, show, complete, edit, and delete tasks.