LISTENINGPOST

Product & engineering

Spec Drift Check

Spec Drift Check. Uses project key, repo, issue id, time window.

Configure this skill

The page and the file follow your answers.

CRM
Email
Chat
Documents
Calendar
Project tools

6 of 6 systems connected

KeepDirectMissing
Your assistantSKILL.md

Download ↓ 
Morning Brief

Build a prioritized brief for today from the caller's calendar, messages, documents and project records, using Keep MCP. Read only.

1. Read today's calendar events, open assigned tasks, direct requests since the last brief and unresolved commitments.
2. Separate active incidents, decisions waiting on the caller, external deadlines and routine work. Check for replies before calling an item outstanding. Rank by consequence and time remaining.
3. Fit proposed actions around fixed meetings and flag conflicting commitments.

Result: a dated brief with urgent changes, commitments, meeting preparation and a feasible next-action list, each tied to its source.

When to use it

Spec Drift Check

What it covers

Inputs

Spec/RFC version, repository and code revision, scope.

Result

Requirement-to-implementation matrix, material differences and verification gaps.

What it uses

Project toolsSlackKeep memoryRead only
For developers

Retrieval instructions

Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.

Data sources

GitHub, Linear, Slack, Keep memory.

Procedure

  1. Resolve inputs for Spec Drift Check: project_key, repo, issue_id, time_window. Default time window: current sprint / since last ship (override if caller provides time_window). Ask only for missing critical inputs.
  2. keep_memory_read for open tasks, decisions, and handoffs relevant to Spec Drift Check (filter out unrelated day-plan noise).
  3. Run keep_search with these skill-specific intents (keep meaning; adjust wording to corpus):

Related skills

Product & engineering →
Support Delivery Pulse→Prepare a support delivery pulse. Uses time window, account, ticket id, severity.Tech Debt Hotspots→Identify technical-debt areas supported by maintenance evidence.Test Gap Suspicions→Identify behavior with missing or weak test evidence.