Verified:GitHub

record

Records architectural decisions and synchronizes corresponding product specification updates during development conversations.

Updated Jun 24, 2026

Search Tags:#product documentation #decision documentation #specification sync #real-time collaboration #ADR recording

Ready to run

npx skills add https://github.com/AvatarGanymede/pcraft --skill record-avatarganymede

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: record
Source: https://github.com/AvatarGanymede/pcraft/tree/main/.agents/skills/record
Command: npx skills add https://github.com/AvatarGanymede/pcraft --skill record-avatarganymede

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps architectural decisions and specifications aligned with work occurring in the conversation. It helps document important choices as they happen and ensures the corresponding specs are updated accordingly.

Core Features & Use Cases

Architectural Decision Recording: Automatically records decisions about architecture or product behavior changes when mentioned.
Spec Updates: Keeps specs synchronized with decisions made during implementation.
Use Case: During development, a designer proposes a change in data models. The Skill creates an ADR, ensuring the spec for that model is updated in parallel.

Quick Start

Initiate the Skill with a simple "Record this" when you discuss a decision or "Create an ADR" to manually record one.

Frequently Asked Questions about record

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep architecture decision records and product specifications synchronized during development?▼

To keep architecture decision records and product specifications synchronized, trigger explicit or automatic documentation updates during development conversations, ensuring corresponding specs are adjusted in parallel with ADRs.

What is the best way to record ADRs during real-time collaboration discussions?▼

Recording ADRs during real-time collaboration is best handled by triggering updates directly within development conversations when architectural choices or product behavior changes are mentioned, capturing decisions as they happen.

How do I automatically update product documentation when data models change?▼

To automatically update product documentation when data models change, use a system that records architectural decisions and automatically adjusts corresponding product specifications in parallel during the conversation.

Can I manually trigger specification sync if an automatic update is missed?▼

Yes, you can manually trigger specification sync by using explicit commands like "Record this" or "Create an ADR" during development conversations, ensuring no architectural decision or spec update is missed.

Does this approach support collaborative decision-making for remote development teams?▼

Yes, this approach supports collaborative decision-making for remote development teams by maintaining architecture and specs in sync through real-time documentation during conversations across the team.