- Home
- Skills
- Technical Documentation
- Team Decision Records: Meeting Notes into ADRs
More screenshots
Works with the AI Agents you already use
Team Decision Records: Meeting Notes into ADRs
Numbering continues the records already in your repository.
$5
Team Decision Records: Meeting Notes into ADRs
Example session with this skill installed
Here are this week's two sync notes and the team chat export. Write the decision records for our repo, with owners and dates.
- Read your context and instructions
- Compiled the team decision records
docs/decisions/0008-dashboard-moves-to-tailwind.md
0008. The dashboard moves to Tailwind CSS
- Status: Accepted
- Date: 2026-03-10
- Decided by: Lina, Priya
Decision
The dashboard moves to Tailwind CSS. New screens first; old screens move when they are touched.
Sources
2026-03-10-weekly-sync.md:23-24: "Final (Lina, Priya): the dashboard moves to Tailwind CSS. New screens first, old screens when they are touched."2026-03-10-weekly-sync.md:21-22: "Tailwind removes about 3,000 lines of CSS; the cleanup removes about 800 and leaves the naming problem."2026-03-03-weekly-sync.md:30-31: "Proposal: maybe move the dashboard to Tailwind? Not decided."
Open questions
- None.
records_check.py:
summary: 0 FIX, 2 ADVICE in decisions (11 records: 9 checked against the notes, 2 earlier; 7 accepted, 1 proposed, 1 superseded; 11 actions; 10 open questions). It checks sources and structure: quotes, names and dates against the notes, numbering, sections and the index. It does not tell whether every decision in the notes was recorded.
Connects securely to your tools. The creator never sees your data.
About this skill
English
For team leads who want this week's decisions written down, with who decided and when.
Give your agent the week's meeting notes and chat exports. You get back decision records ready to commit to your repository, one per decision, each with who decided, when, and the exact words from the notes, plus an action list with owners and due dates.
What you get each run
docs/decisions/NNNN-title.md: one record per decision in the ADR style: status, date, decided by, context, decision, consequences, alternatives mentioned, sources quoted word for word with file and line, and open questions. Numbering continues the records already in your repository.docs/decisions/README.md: the index of all records with their status and date.docs/decisions/actions.md: each action with its owner, due date, source and status.decisions.html: everything on one printable page to share in the next meeting.
Read from your notes
A bundled Python script (standard library, read-only, no network calls) reads Markdown or text notes and dated chat exports. It lists the lines that look like decisions ("decided", "agreed", "we will", «قررنا», «اتفقنا») and actions with owners and dates, each with its file and line, and flags hedges such as "maybe", "proposal" or "if". These are candidates: the agent confirms the unclear ones with you before writing a record.
Nothing invented
A record is Accepted only when the notes say the decision was made; otherwise it is Proposed and the open point becomes a question. Names and dates appear only as the notes give them. A due date such as "next Friday" becomes a question, not a guessed date. A decision that replaces an earlier one is linked both ways.
Checked, not just written
A checker confirms that every quote is in the notes letter for letter at the cited line, every name and date appears in the source, numbering has no gaps or duplicates, the index agrees with the records, and every section is present. The agent fixes and checks again until no FIX is left.
Honest about its limits
The checker verifies sources and structure. It does not tell whether every decision in the notes was recorded, and the word lists can miss unusual phrasing, so the agent reads the notes as well as the candidates.
One week, minutes
Team Decision Records turns this week's notes into records you commit, going forward. For a whole project's past decisions across git, tickets and notes, use Decision Trail.
Arabic
Records can be written in Arabic from Arabic notes, with a right-to-left page; quotes keep the wording of the notes, and file names stay in Latin letters.
In the download: SKILL.md, the scripts, references (the record format, how to read notes and tell a decision from a proposal), and two complete examples so you can see the output before you buy: an English team's two weekly syncs and chat, and an Arabic team's meetings and chat export, each with 9 new records and the action list.
بالعربي
لقادة الفرق الذين يريدون قرارات الأسبوع مكتوبة، بمن قرر ومتى.
أعطِ وكيلك محاضر اجتماعات الأسبوع وتصدير المحادثات. تستلم سجلات قرارات جاهزة لإضافتها إلى المستودع، سجل لكل قرار، فيه من قرر ومتى والكلمات نفسها من المحضر، مع قائمة مهام بأصحابها ومواعيدها.
ماذا تستلم في كل مرة
- ملفات
docs/decisions/NNNN-title.md: سجل لكل قرار بأسلوب ADR: الحالة، والتاريخ، ومن قرر، والسياق، والقرار، والنتائج، والبدائل المذكورة، والمصادر منقولة حرفيًا مع الملف والسطر، وأسئلة مفتوحة. والترقيم يكمل السجلات الموجودة في مستودعك. - ملف
docs/decisions/README.md: فهرس كل السجلات بحالتها وتاريخها. - ملف
docs/decisions/actions.md: كل مهمة مع صاحبها وموعدها ومصدرها وحالتها. - صفحة
decisions.html: كل شيء في صفحة واحدة قابلة للطباعة لمشاركتها في الاجتماع القادم.
من محاضرك أنت
سكربت بايثون مرفق (يقرأ فقط، بلا اتصال بالشبكة) يقرأ المحاضر وتصدير المحادثات المؤرخة. يسرد الأسطر التي تشبه القرارات («قررنا»، «اتفقنا»، "decided"، "agreed") والمهام بأصحابها ومواعيدها، مع الملف والسطر، وينبّه على كلمات التردد مثل «ربما» و«اقتراح» و«إذا». هذه مرشحات فقط: الوكيل يتأكد منك في غير الواضح قبل كتابة السجل.
لا شيء مخترع
السجل "مقبول" فقط إذا قالت المحاضر إن القرار اتُّخذ؛ وإلا فهو "مقترح" والنقطة المفتوحة تصير سؤالًا. والأسماء والتواريخ تظهر كما في المحاضر فقط. وموعد مثل «الجمعة القادمة» يصير سؤالًا، لا تاريخًا مخمّنًا.
مدقَّق، لا مكتوب فقط
أداة فحص تتأكد أن كل اقتباس موجود في المحضر حرفًا بحرف في السطر المذكور، وكل اسم وتاريخ موجود في المصدر، والترقيم بلا فجوات ولا تكرار، والفهرس يطابق السجلات. يصلح الوكيل ويعيد الفحص حتى لا يبقى أي FIX.
صادق في حدوده
الأداة تتحقق من المصادر والبنية، ولا تعرف هل سُجّل كل قرار في المحاضر، وقوائم الكلمات قد تفوتها صياغة غير معتادة، لذلك يقرأ الوكيل المحاضر نفسها لا المرشحات فقط.
أسبوع واحد، في دقائق
هذه المهارة تحوّل محاضر هذا الأسبوع إلى سجلات تضيفها للمستودع من الآن فصاعدًا. لقرارات مشروع كامل في الماضي عبر git والتذاكر والمحاضر، استعمل Decision Trail.
العربية
تُكتب السجلات بالعربي من محاضر عربية، مع صفحة من اليمين إلى اليسار؛ والاقتباسات تحفظ كلام المحضر، وأسماء الملفات بالحروف اللاتينية.
داخل الملف: ملف SKILL.md، والسكربتات، والمراجع، ومثالان كاملان لترى النتيجة قبل الشراء: اجتماعان أسبوعيان ومحادثة لفريق إنجليزي، واجتماعات ومحادثة لفريق عربي، ولكل منهما 9 سجلات جديدة وقائمة المهام.
Reads Markdown and text notes and dated chat exports that you give it; it does not connect to Slack, Teams or WhatsApp, so you export the chats yourself. Number-only dates (like 03/04/2026) are read only when you say which order they use. Decision and action lines are found with word lists and are candidates the agent confirms; unusual phrasing can be missed, so the agent reads the notes too. The checker verifies quotes, names, dates, numbering and sections, not whether every decision in the notes was recorded. decisions.html loads its fonts from Google Fonts when online and falls back to system fonts offline. يقرأ ما تعطيه من محاضر، والأداة لا تعرف هل سُجّل كل قرار.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 3 days ago
Requires
Permissions
Reads the notes and chat exports you give it and the existing decision records in your repository, writes the new records, README.md and actions.md in docs/decisions and decisions.html in a work folder, and runs its local Python scripts (notes_scan.py, records_check.py, make_page.py). The scripts make no network calls, and nothing is committed or pushed unless you ask. يقرأ المحاضر ويكتب ملفات السجلات فقط.