SkillVaultskills Browse all 500 skills

Productivity · Version 1.7.0 · Reviewed 2026-08-02

Meeting Notes to Engineering Tasks

Turn engineering context into a reliable artifact for task extraction and acceptance criteria with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Converts messy meeting notes into scoped, assignable tasks with acceptance criteria and open questions.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Task extraction
  • Acceptance criteria
  • Owner assignment

How Meeting Notes to Engineering Tasks works

You provide

Repository access, entry points, and the target change

It inspects

Real execution path for task extraction, not naming

It decides

A acceptance criteria explanation with safe change seams

You verify

Claims confirmed against code paths or a test

What it checks first

Meeting Notes to Engineering Tasks converts messy meeting notes into scoped, assignable tasks with acceptance criteria and open questions. Use it when the work involves Task extraction, Acceptance criteria, Owner assignment.

  1. The entry points and the data flow between them, which is the fastest way to build an accurate mental model.
  2. Where behavior is actually decided, rather than where it appears to be configured.
  3. Which parts change frequently, since those carry the most current knowledge and the most risk.
  4. The seams where a change can be made safely without a wide blast radius.

Failure modes it recognizes

  • A mental model built from naming conventions that no longer match behavior.
  • Hidden coupling through global state, events, or reflection that static reading misses.
  • Dead code that appears authoritative and misleads the reader.
  • Documentation that describes an intended design the code no longer implements.

Answers it will reject

  • Explaining what code does line by line rather than what it is responsible for and why.
  • Trusting comments and documentation over the executing code path.
  • Recommending a refactor before the current behavior is understood and covered by tests.

Decision rules it applies

  • Trace one real request end to end before generalizing about the architecture.
  • Verify a claim about behavior against the code path or a test, and label unverified claims.
  • Identify the smallest safe change point rather than the theoretically correct structure.

Evidence it asks for

  • Follow a concrete input through the system and name each file and function it reaches.
  • Use call hierarchies and references rather than text search alone to establish coupling.
  • Confirm behavior with an executable test before changing it.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for task extraction.
  2. Organize acceptance criteria around the reader's next decision or action rather than the source order.
  3. Draft owner assignment with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Task extraction assessment
  • Acceptance criteria decision and action plan
  • Owner assignment verification checklist

Evidence requirements

  • Source code, discussion, notes, or existing artifact
  • Audience, decision, and acceptance criteria
  • Repository conventions and constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Turn these standup notes into tickets with clear acceptance criteria.

Expected output

Extracted seven actionable items and separated three decisions that are not tasks. Two items lacked acceptance criteria, so those are listed as questions...

Boundaries and compatibility

Ideal for

  • Task extraction: produce a decision or artifact grounded in supplied evidence.
  • Acceptance criteria: produce a decision or artifact grounded in supplied evidence.
  • Owner assignment: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing repository behavior or decisions
  • Replacing review by the accountable owner

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.