etkm-project-standard

Enforce Project Card, QC gates, and handoff briefs before production.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-project-standard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etkm-project-standard
Source: https://github.com/easttxkravmaga/Claude/tree/main/skills/etkm-project-standard
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-project-standard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires etkm-brand-kit, etkm-brand-foundation, etkm-format-standards, etkm-deliverable-qc, etkm-ai-roles.

What problem does it solve?

This Skill ensures every ETKM project starts from a locked, standardized packaging layer by enforcing a completed Project Card, mandatory QC gates, and proper handoff briefs before production.

Core Features & Use Cases

  • Establishes a six-layer framework (Project Identity, Project Card, Agent Stack, Gates, Handoff, Benchmark) so projects are consistently structured.
  • Coordinates with etkm-brand-kit, etkm-brand-foundation, etkm-format-standards, etkm-deliverable-qc, and etkm-ai-roles to govern production readiness.
  • Used at project initiation, during scoping, before handoffs to Manus or Claude Code, and prior to production audits to prevent improvisation.

Quick Start

Load this skill at the start of any new project to establish the six-layer framework and verify that a completed Project Card exists before production begins.

Frequently Asked Questions about etkm-project-standard

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

FAQPage Schema
How do I enforce production readiness before starting a project handoff?

To enforce production readiness, load this skill at project initiation to verify a completed Project Card, execute mandatory QC gates, and finalize a proper handoff Brief before any work starts.

What is a Project Card and when do I need it for project packaging?

A Project Card is a mandatory layer within a six-layer framework required for project packaging. You need it during scoping sessions, production audits, and before any handoffs to Manus or Claude Code to prevent improvisation.

How do I structure a project workflow with QC gates and a handoff brief?

Structure your project workflow by applying the six-layer framework: Project Identity, Project Card, Agent Stack, Gates, Handoff, and Benchmark. This establishes standardized packaging and enforces QC gates before production begins.

Do I need brand-kit and format-standards dependencies to use this production standard?

Yes, this production standard explicitly loads and coordinates with etkm-brand-kit, etkm-brand-foundation, etkm-format-standards, etkm-deliverable-qc, and etkm-ai-roles to govern production readiness and ensure consistent project packaging.

Can I use this workflow standard for scoping sessions and quality audits?

Yes, this workflow standard applies to new projects, scoping sessions, handoffs to Manus or Claude Code, and quality audits. It prevents improvisation by ensuring a completed Project Card exists before production.

Why does my project workflow fail without a completed Project Card?

Your project workflow fails because the production standard requires a completed Project Card to establish a locked, standardized packaging layer. Without it, mandatory QC gates cannot execute and handoffs are blocked to prevent improvisation.