intent-trace

Trace product and engineering artifacts to founder intent and declared sources.

4|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/vmobifystudio/app-dev-team --skill intent-trace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intent-trace
Source: https://github.com/vmobifystudio/app-dev-team/tree/main/skills/intent-trace
Command: npx skills add https://github.com/vmobifystudio/app-dev-team --skill intent-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents interpretation drift across product and engineering artifacts by making every decision, requirement, implementation, test, analytics event, and release traceable to its source and verifier.

Core Features & Use Cases

  • Founder Intent Records: Preserve the original brief, constraints, transcripts, examples, and append-only decisions as the external source of truth.
  • End-to-End Traceability: Assign structured IDs and source, verifier, state, and revision metadata across goals, requirements, criteria, designs, tickets, code, tests, evidence, analytics, and releases.
  • Conflict and Gate Detection: Resolve competing claims using explicit precedence rules and identify conditional founder approvals for pricing, sensitive data, legal disclosures, destructive migrations, and other risk triggers.
  • Use Case: Apply it before scope lock and at every hand-off to verify that a requirement has a founder source, current acceptance criteria, implementation coverage, tests, and release evidence.

Quick Start

Use the intent-trace skill to audit the project's traceability chain, conflicts, and conditional founder gates from the repository root.

Frequently Asked Questions about intent-trace

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

FAQPage Schema
How do I trace product requirements back to original founder intent?

Tracing requirements to founder intent involves assigning structured IDs and metadata across goals, tickets, code, and releases to verify every artifact has a declared source, verifier, state, and revision.

What is end-to-end traceability in software engineering?

End-to-end traceability prevents interpretation drift by linking every product decision, implementation, test, and release event back to its original source and verifier through structured metadata.

How do I resolve conflicting acceptance criteria during release governance?

Resolve conflicting acceptance criteria by applying explicit precedence rules and append-only decision records to enforce source, state, and revision metadata across competing claims.

When do I need conditional founder gates for scope locking?

Conditional founder gates are needed during scope locking for risk triggers like pricing changes, sensitive data handling, legal disclosures, and destructive migrations requiring explicit founder approval.

Can I audit traceability chains from the repository root?

Audit traceability chains from the repository root by verifying each requirement has a founder source, current acceptance criteria, implementation coverage, tests, and release evidence before hand-offs.