Skip to content

Feature: spec directory #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jsls2517 wants to merge 3 commits into
base: main
Choose a base branch
from
+13 −4
Open

Feature: spec directory #93

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
70b4385
Change spec save location to feature-specific directory
jsls2517 Apr 23, 2026
2b40508
Revise saving paths for plans and task lists
jsls2517 Apr 23, 2026
6479476
Clarify artifact locations and management in docs
jsls2517 Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .claude/commands/plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,8 @@ Read the existing spec (SPEC.md or equivalent) and the relevant codebase section
5. Add checkpoints between phases
6. Present the plan for human review

Save the plan to tasks/plan.md and task list to tasks/todo.md.
Save the plan and task list to the same feature directory:
- docs/features/[feature-name]/plan.md
- docs/features/[feature-name]/todo.md

This keeps all feature artifacts together and enables multiple simultaneous features.
6 changes: 5 additions & 1 deletion .claude/commands/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,4 +12,8 @@ Begin by understanding what the user wants to build. Ask clarifying questions ab

Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.

Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
Save the spec to a feature-specific directory: docs/features/[feature-name]/spec.md

First, determine the feature name based on the objective (e.g., "user-authentication", "payment-integration", "dashboard-analytics"). Create the directory structure docs/features/[feature-name]/ and save the spec as spec.md within that directory.

This prevents spec overwriting and enables multiple simultaneous features. Confirm with the user before proceeding.
5 changes: 3 additions & 2 deletions docs/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,11 +127,12 @@ Load a reference when you need detailed patterns beyond what the skill covers.

## Spec and task artifacts

The `/spec` and `/plan` commands create working artifacts (`SPEC.md`, `tasks/plan.md`, `tasks/todo.md`). Treat them as **living documents** while the work is in progress:
The `/spec` and `/plan` commands create working artifacts in feature-specific directories (`docs/features/[feature-name]/spec.md`, `docs/features/[feature-name]/plan.md`, `docs/features/[feature-name]/todo.md`). Treat them as **living documents** while the work is in progress:

- Keep them in version control during development so the human and the agent have a shared source of truth.
- Update them when scope or decisions change.
- If your repo doesn’t want these files long‑term, delete them before merge or add the folder to `.gitignore` — the workflow doesn’t require them to be permanent.
- Feature-specific organization prevents overwriting and enables multiple simultaneous features.
- If your repo doesn't want these files long-term, delete them before merge or add `docs/features/` to `.gitignore` - the workflow doesn't require them to be permanent.

## Tips

Expand Down