Add changeset survey to task generation template

[Copilot]

The create-tasks.md template lacked visibility into which files already exist versus those requiring creation. This made it difficult to assess implementation scope upfront.

Changes

• Process: Added "Survey Existing Codebase" step before task generation to identify and classify all relevant files
• Output Format: Replaced "Relevant Files" bullet list with "Changeset Survey" table showing file status
• Status Markers: Introduced add, edit, unchanged, delete classification for each file

Example

Before (bullet list):

## Relevant Files
- `components/profile/UploadPhoto.tsx` - Upload form component
- `lib/storage/s3.ts` - S3 upload helper functions

After (table with status):

## Changeset Survey

| Path                                 | Status | Description                    |
|--------------------------------------|--------|--------------------------------|
| `components/profile/UploadPhoto.tsx` | add    | Upload form component          |
| `lib/storage/s3.ts`                  | edit   | Add S3 upload helper functions |

The table format makes file creation versus modification explicit at a glance, reducing ambiguity in implementation planning.

Original prompt

The create-tasks.md template already includes a "Relevant Files" section to list the files to be created or changed for the feature (a "changeset survey").
To make your script more explicit, adjust it to:

1. Survey the codebase for existing related files (summarize current state).
2. Print a clear changeset (files added/modified/removed).
3. Note gaps or required new files.

Suggested revision to your process section:

Add before "Generate Tasks":

Survey Existing Codebase: List all files related to the feature’s implementation (existing and required). Note anything that will be added, changed, or removed.

Update the output to:

• Print the changeset (with “add”, “edit”, “delete” or “unchanged” markers).
• Note necessary new files versus existing files to be modified.

Sample Markdown Output Section:

## Changeset Survey

| Path                           | Status    | Description                  |
|---------------------------------|-----------|------------------------------|
| `components/profile/UploadPhoto.tsx`      | add       | New upload form component    |
| `components/profile/ProfileImage.tsx`     | edit      | Update to support new image  |
| `lib/storage/s3.ts`                        | unchanged | Helper functions             |
| `api/profile/picture.ts`                   | add       | Upload endpoint              |
| `pages/api/profile/picture.test.ts`        | add       | Unit tests for endpoint      |

*Files not found and marked "add" will need to be created. Files marked "edit" will be modified for this feature.*

Process update example:

3. **Survey Existing Codebase:**  
    - Identify which files already exist and which need to be created or edited for this feature.
    - Report a changeset table in your output.

Would you like a pull request to update the create-tasks.md template with these changes? If yes, should the changeset be Markdown, table, or another format?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.