linked-intent-dev

Execute a six-phase software development workflow from HLD check to code implementation.

Updated Apr 26, 2026

Search Tags:#code review #structured development #software workflow #intent alignment #software engineering practices

Ready to run

npx skills add https://github.com/jmbeach/vat --skill linked-intent-dev-jmbeach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: linked-intent-dev
Source: https://github.com/jmbeach/vat/tree/main/.claude/skills/linked-intent-dev
Command: npx skills add https://github.com/jmbeach/vat --skill linked-intent-dev-jmbeach

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, mode-aware six-phase workflow to ensure the quality and consistency of software development, focusing on aligning developer output with user intent.

Core Features & Use Cases

Six-Phase Workflow: Ensures code changes are meticulously reviewed and tested against user intent.
Mode-aware Triggering: Full or scoped triggering based on project configuration.
Coherence Verification: Checks the consistency of specs, LLDs, and HLDs.
Cascade Discipline: Maintains coherence across related code components.
Bug Fixes and LID-on-LID: Ensures even bug fixes adhere to the structured process.

Quick Start

Use the linked-intent-dev skill to begin a code change by checking the high-level design at 'docs/high-level-design.md'.

Frequently Asked Questions about linked-intent-dev

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

FAQPage Schema

How do I maintain intent alignment across high-level design and low-level design phases?▼

Intent alignment is maintained through a structured software workflow that verifies coherence across HLDs, LLDs, and EARS specs. This ensures your code implementation consistently matches the original user intent throughout development.

What is a structured software development workflow with EARS spec updates?▼

A structured software development workflow with EARS spec updates is a six-phase process ensuring quality and consistency. It checks high-level designs, drafts LLDs, updates EARS specs, audits edges, tests, and implements code to align output with intent.

How do I start a code change using a mode-aware software workflow?▼

Start a code change by checking your high-level design at docs/high-level-design.md. The mode-aware workflow then triggers full or scoped development phases based on your project configuration to guide implementation.

Can I use a structured development workflow for bug fixes without breaking coherence?▼

Yes, you can use this structured development workflow for bug fixes through its LID-on-LID capability. It ensures even bug fixes adhere to the structured process, maintaining strict cascade discipline and coherence across related code components.

When do I need an edge audit in my software engineering practices?▼

You need an edge audit during the testing phase of a structured software workflow to catch boundary issues before code implementation. It verifies that your LLDs and EARS specs handle edge cases coherently with the high-level design.