feature-development
The /feature-development command provides a structured workflow scaffold for implementing new features in the everything-claude-code project. Use this when adding feature implementations to guide your approach through understanding current state, making minimal coherent changes, running relevant verification, and following typical commit patterns like adding implementation, tests, and documentation updates.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/affaan-m/ECC/HEAD/.claude/commands/feature-development.md -o ~/.claude/commands/feature-development.mdfeature-development.md
# /feature-development Use this workflow when working on **feature-development** in `everything-claude-code`. ## Goal Standard feature implementation workflow ## Common Files - `manifests/*` - `schemas/*` - `**/*.test.*` - `**/api/**` ## Suggested Sequence 1. Understand the current state and failure mode before editing. 2. Make the smallest coherent change that satisfies the workflow goal. 3. Run the most relevant verification for touched files. 4. Summarize what changed and what still needs review. ## Typical Commit Signals - Add feature implementation - Add tests for feature - Update documentation ## Notes - Treat this as a scaffold, not a hard-coded script. - Update the command if the workflow evolves materially.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
>
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
>