project-decision-profile

Maintains a project decision profile file using ASK, RESOLVE, and UNDECIDED tokens.

39|3|Updated Jul 28, 2025
One-click install
npx skills add https://github.com/mzivkovicdev/spring-crud-generator --skill project-decision-profile-mzivkovicdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-decision-profile
Source: https://github.com/mzivkovicdev/spring-crud-generator/tree/main/.agents/skills/project-decision-profile
Command: npx skills add https://github.com/mzivkovicdev/spring-crud-generator --skill project-decision-profile-mzivkovicdev

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Software projects accumulate implicit decisions about databases, versions, contracts, security, and testing that different tasks then guess inconsistently. This Skill centralizes those decisions in a single docs/project-profile.md file so no task has to guess and no two tasks guess differently. ## Core Features & Use Cases - Decision token vocabulary: Enforces exactly three tokens — ASK (user must answer, blocks work), RESOLVE (agent looks up and records with date), and UNDECIDED (deliberate deferral with a forcing condition). - Profile gate: Blocks production code changes until every decision the task depends on is recorded, with narrow exceptions for documentation-only edits. - Template and fallback rules: Ships a copy-ready project profile template covering platform, persistence, API contract, security, observability, caching, performance, and testing decisions, with fallbacks living only in the template's Fallback column. - Use Case: Before implementing a new Spring Boot feature, an agent checks docs/project-profile.md, finds the database engine row is a bare ASK with no fallback, and asks the user once instead of silently picking H2 from a test dependency. ## Quick Start Ask the agent to create docs/project-profile.md from the template and fill in every decision the current task depends on before writing any production code.

Frequently Asked Questions about project-decision-profile

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

FAQPage Schema
How do I record project architecture decisions for AI coding agents?▼

Copy the project profile template to docs/project-profile.md and fill each row with a value or a decision token. Agents read this file before writing code, so decisions like database engine, service shape, and contract direction are recorded once instead of guessed per task.

What do the ASK, RESOLVE, and UNDECIDED tokens mean?▼

ASK must be answered by the user and blocks dependent work unless the template row has a fallback. RESOLVE is looked up by the agent and recorded with a date. UNDECIDED is a deliberate deferral that names what will force the decision.

When can I skip creating the project decision profile?▼

Documentation, comment, and formatting changes need no profile. A task may also proceed on a partial profile as long as every decision that specific task touches is recorded; all other production code work is gated on the profile.

Can an agent fill in missing profile values from memory or test dependencies?▼

No. Values must never be written from memory, inferred from test dependencies, or copied from examples. An unresolvable RESOLVE becomes UNDECIDED with the reason recorded, because a remembered version is a guess that later tasks will trust.

Which decisions block work and which have fallbacks?▼

ASK rows with an empty Fallback column block, such as database engine and tenancy model. Rows with a recorded fallback, like dependency version policy or request budget, are applied, written into the Value column, and reported in the handoff.