skills.rest
thrillmade
thrillmadeOFFICIAL
Explore all skills by this author →
GitHub

logmind

Log architectural decisions before code changes in Git projects.

1|Updated May 15, 2026
Search Tags:#code review#version control#decision logging#project documentation#architectural decisions
One-click install
npx skills add https://github.com/thrillmade/agent-skills --skill logmind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: logmind
Source: https://github.com/thrillmade/agent-skills/tree/main/skills/logmind
Command: npx skills add https://github.com/thrillmade/agent-skills --skill logmind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all architectural decisions are logged and documented as you work, promoting clarity and preventing future rework.

Core Features & Use Cases

  • Decision Logging: Automatically log decisions before writing code, making changes, or adding dependencies.
  • Branch Awareness: Differentiate between main branch and feature branch logging.
  • Documentation Generation: Generate documentation like docs/decisions.md and docs/timeline.md for project history and reference.
  • Use Case: For instance, when starting a new feature branch, use this Skill to log the architectural choice of using PostgreSQL for the database.

Quick Start

Use the logmind skill to log a decision about using PostgreSQL for the primary database.

Frequently Asked Questions about logmind

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

FAQPage Schema
How do I automate architectural decision logging in my software project?▼

Automating architectural decision logging requires setting up a configuration file to track choices before implementation. This approach ensures decisions are documented on both main and feature branches, reducing rework and maintaining project clarity throughout the development lifecycle.

How do I generate documentation for project history and architectural decisions?▼

Generating project documentation involves logging architectural decisions before writing code. This process automatically outputs files like docs/decisions.md and docs/timeline.md, providing a clear project history and reference for your team's architectural choices.

Can I use Git version control to track architectural decisions?▼

Yes, you can use Git version control to track architectural decisions. The system applies to projects using Git, differentiating between main and feature branch logging to maintain a clear timeline of architectural choices and project documentation.

Do I need a specific configuration file to log architectural decisions?▼

Yes, you need a .logmind/config.yml file to configure the decision logging tool. This configuration is required to automate the tracking of architectural decisions and generate the corresponding project documentation.

When should I log architectural decisions before starting implementation?▼

You should log architectural decisions before writing code, making changes, or adding dependencies. Logging choices beforehand, such as selecting a database, ensures the decision is documented and prevents future rework by maintaining project clarity.

Related Skills

Explore More Software Engineering Skills→
opencueopencue
3

speckit-git-commit

Automatically stage and commit changes after Spec Kit commands.

Official
Basic
luyzkkluyzkk

decision-registry

Record and retrieve architectural decisions in ADR or decisions.md files.

Community
Intermediate
CharGrnmnCharGrnmn
1

gpd-complete-milestone

Mark completed research milestones, archive documents, and tag them in version control.

Community
Advanced
Lands-1203Lands-1203
40

f2s-doc-arch

Generate project architecture description drafts from documentation or code.

Community
Intermediate