capability-assess-stack

Assess and record technology stack decisions with version tracking across project lifecycle.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/learnn-com/engineering-kb --skill capability-assess-stack-learnn-com
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capability-assess-stack
Source: https://github.com/learnn-com/engineering-kb/tree/main/.skills/capability-assess-stack
Command: npx skills add https://github.com/learnn-com/engineering-kb --skill capability-assess-stack-learnn-com

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often lose track of which technologies, frameworks, and library versions are approved for a project, leading to inconsistent dependencies and undocumented decisions. This Skill maintains a versioned tech stack registry and records every stack decision as an ADL or ADR. ## Core Features & Use Cases - Resolution Cascade: Resolves stack choices via Argument Override, existing Adoption, or Full Assessment, with automatic lifecycle mode detection (bootstrap, implementation, review). - Version-Tracked Registry: Writes and updates tech-stack.md with mandatory versions for every entry while respecting section ownership shared with testing and AI assessment skills. - Decision Recording: Composes /capability-record-decision to backfill or create decision records for every approved stack change. - Use Case: During code review, an unlisted dependency like zod@3.22 is detected; the Skill presents approve/reject options, adds it to tech-stack.md with its version, and records the decision. ## Quick Start Ask the AI to assess the technology stack for the project, or to evaluate adding a specific dependency such as zod@3.22 to the existing tech stack.

Frequently Asked Questions about capability-assess-stack

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

FAQPage Schema
How do I assess and document a project's technology stack?▼

Run the assessment in bootstrap mode to evaluate language, framework, runtime, database, and core libraries against project guidelines. The result is written to tech-stack.md with versions for every entry, and the decision is recorded as an ADL or ADR.

How do I add a new dependency to an existing tech stack?▼

Invoke the skill in implementation mode with the dependency in name@version format, such as zod@3.22. It validates compatibility with the existing stack, warns about version or category conflicts, then adds the entry and records the decision.

What happens when code review finds an unlisted dependency?▼

Review mode presents the unlisted dependency with approve or reject options. Approving adds it to tech-stack.md with its version and records a decision; rejecting reports it back to the review process as a changes-requested finding.

Does the tech stack registry track dependency versions?▼

Yes, every entry in tech-stack.md must include a version with at least major.minor precision. Version updates go through the same assessment flow, checking compatibility before updating the adoption file and writing a decision record.

Can multiple assessment skills write to the same tech-stack file?▼

Yes, through section ownership. This skill owns core sections like language, framework, and runtime, while testing and AI sections are owned by their respective skills, which this skill reads but never writes.