mirror of
https://github.com/affaan-m/ECC.git
synced 2026-09-17 23:28:04 +02:00
Bechor SimhaevandAlex Schmitt
ea2ec0d249
Nine command files spell the key with an underscore while six other files in this repository already use `allowed-tools`. Claude Code reads the hyphenated form, so the underscored key is unrecognized and the tool pre-approval it is meant to grant never applies.
38 lines
918 B
Markdown
38 lines
918 B
Markdown
---
|
|
name: feature-development
|
|
description: Workflow command scaffold for feature-development in everything-claude-code.
|
|
allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob"]
|
|
---
|
|
|
|
# /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. |