develop-a-feature

Name: develop-a-feature
Availability: InStock
Author: Compartment

Coordinate feature implementation with preflight validation and diff-triggered checks.

229|5|Updated May 25, 2026

Search Tags:#workflow #planning #engineering #feature #preflight #repo #change-management

Ready to run

npx skills add https://github.com/compartmentdev/compartment --skill develop-a-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: develop-a-feature
Source: https://github.com/compartmentdev/compartment/tree/main/.codex/skills/develop-a-feature
Command: npx skills add https://github.com/compartmentdev/compartment --skill develop-a-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated, guardrail-driven feature work to ensure changes follow ownership boundaries, preflight validation, and minimal surface edits.

Core Features & Use Cases

Preflight-driven workflow: requires a preflight subagent before any changes.
Minimal surface edits: changes target the smallest owning surface on one canonical path.
Diff-triggered validation: runs only the necessary checks and tests.

Quick Start

Start a feature by loading the required preflight brief, then edit the smallest owning surface on one canonical path and run only diff-triggered checks.

Frequently Asked Questions about develop-a-feature

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

FAQPage Schema

How do I enforce ownership boundaries and run preflight checks for repository feature work?▼

Preflight checks for repository feature work enforce ownership boundaries by requiring a preflight subagent before edits. This ensures changes target the smallest owning surface on one canonical path while running only diff-triggered validation.

What is a diff-triggered validation workflow for engineering features?▼

A diff-triggered validation workflow runs only the necessary checks and tests based on the actual code changes. It ensures lint, typecheck, tests, and preflight validation execute within a single change while enforcing ownership boundaries.

Can I run lint, typecheck, and tests within a single feature change workflow?▼

Yes, you can run lint, typecheck, and tests within a single feature change workflow. The process satisfies requirements to execute these checks alongside the preflight validation matrix while enforcing ownership boundaries.

How do I start a feature by loading a preflight brief before making code changes?▼

Start a feature by loading the required preflight brief subagent. After the preflight completes, edit the smallest owning surface on one canonical path and run only diff-triggered checks to validate your changes.

When should I not use a minimal surface edit approach for feature planning?▼

You should not use a minimal surface edit approach when a feature requires changes across multiple canonical paths or lacks a clear single owning surface. The workflow strictly targets the smallest owning surface to enforce boundaries.