engram-sdd-flow
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Spec-Driven Development workflow for Engram. Trigger: When user requests SDD or multi-phase implementation planning.
Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.
API contract guardrails for Engram server changes. Trigger: Any route, handler, payload, or status code modification.
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
Transform CHANGELOG entries into social content (LinkedIn, Twitter/X, Newsletter, Slack) in FR + EN. Use after releases or weekly to generate ready-to-post content from guide updates.
Compare different approaches to solve the same problem
Interactive skill assessment with personalized learning path generation
Add descriptive prose to bare sections in whitepapers (FR + EN) using 9 parallel agents
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack