Where are the technical decisions stored?

Decisions are stored as a new file in a Google Drive folder you specify. It never saves to the Drive root and typically defaults to the same folder as your PRD.

What happens after the decisions are recorded?

The skill provides a Drive URL which can be added to your project manifest. This serves as the reference point for creating milestones and issues in your project management tool.

Can it help me follow my team's specific coding standards?

Yes. It can load existing team convention documents from Drive to use as context, helping you decide whether to follow established patterns or document necessary deviations.

Does this skill support full Architectural Decision Records (ADRs)?

It focuses on a simplified format capturing 'what was decided and why' rather than a full ADR ceremony, making it faster and more practical for agile development teams.

How does it access my Google Drive?

The skill uses the Google Drive MCP tools to list accounts and search for files. It requires your explicit permission to access specific accounts and folders during the session.

Technical Decision Tracker

Name: Technical Decision Tracker
Author: codingthefuturewithai

bycodingthefuturewithai

0•

コラボレーションツール

Records and manages technology stack choices by syncing project requirements and team conventions with Google Drive.

The Technical Decision Tracker skill empowers developers to define and document their project's architectural foundation without the overhead of complex ADR ceremonies. By integrating directly with Google Drive, it pulls context from PRDs and existing team conventions to help you make informed decisions about languages, frameworks, and infrastructure. This skill facilitates a focused dialogue to capture the 'what' and 'why' behind every major choice, storing the result as a single source of truth that informs sprint planning, issue creation, and code implementation.

主な機能

01Project Manifest Integration: Generates documented URLs ready to be recorded in project manifests and task trackers.

02Structured Decision Capture: Simplifies technical documentation by focusing on the 'what', 'why', and key caveats.

03Convention Matching: Surfaces existing team standards and conventions to ensure consistency across projects.

04PRD Contextualization: Automatically analyzes project requirements to align tech choices with business goals.

05Google Drive Integration: Seamlessly search, load, and save technical documentation directly within Claude.

060 GitHub stars

ユースケース

01Documenting specific deviations from standard team conventions for unique project needs.

02Preparing technical context for sprint planning to ensure engineers have a clear implementation roadmap.

03Kickstarting a new repository by defining the core tech stack and architectural approach.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add codingthefuturewithai/claude-code-primitives tech-decisions

For use in Claude.ai and ChatGPT

主な機能

01Project Manifest Integration: Generates documented URLs ready to be recorded in project manifests and task trackers.

02Structured Decision Capture: Simplifies technical documentation by focusing on the 'what', 'why', and key caveats.

03Convention Matching: Surfaces existing team standards and conventions to ensure consistency across projects.

04PRD Contextualization: Automatically analyzes project requirements to align tech choices with business goals.

05Google Drive Integration: Seamlessly search, load, and save technical documentation directly within Claude.

060 GitHub stars

ユースケース

01Documenting specific deviations from standard team conventions for unique project needs.

02Preparing technical context for sprint planning to ensure engineers have a clear implementation roadmap.

03Kickstarting a new repository by defining the core tech stack and architectural approach.