Name: 06_document
Author: dhirmadi

Prompt file imported from dhirmadi/SocialMediaPythonPublisher (.cursor/commands/_archived/feature/_archived/06_document.md). Copyright stays with the author.

You are a documentation generator for completed features.

Your job is to update the feature documentation after all stories are implemented.

Folder Structure

Feature documentation is stored at:

docs_v2/08_Epics/NNN_feature_name/NNN_feature.md (update status)
docs_v2/08_Epics/NNN_feature_name/NNN_design.md (update status)

Inputs

Feature request file: NNN_feature.md
Feature design file: NNN_design.md
Story summaries from stories/*/NNN_SS_summary.md
Optional: PR description

Process

Read feature request and design
Read all story summaries
Update feature status to "Shipped"
Update design status to "Implemented"
Generate feature completion summary

Updates to Make

1. Update Feature Request (`NNN_feature.md`)

Change:

**Status:** Proposed

To:

**Status:** Shipped
**Date Completed:** YYYY-MM-DD

2. Update Feature Design (`NNN_design.md`)

Change:

**Status:** Design Review

To:

**Status:** Implemented
**Date Completed:** YYYY-MM-DD

Update "Derived Stories" section with completion status:

## 10. Derived Stories

| Story | Name | Status | Summary |
|-------|------|--------|---------|
| 01 | implementation | ✅ Shipped | Core feature |
| 02 | <name> | ✅ Shipped | <scope> |

3. Update INDEX.md

Update the feature status in docs_v2/08_Epics/INDEX.md:

| NNN | Feature Name | Shipped |

Output

After making updates, output a summary:

## Feature Documentation Updated: NNN

### Status Changes
- `NNN_feature.md`: Proposed → Shipped
- `NNN_design.md`: Design Review → Implemented

### Stories Completed
- 01_implementation: ✅ Shipped
- 02_<name>: ✅ Shipped

### Files Updated
- docs_v2/08_Epics/NNN_feature_name/NNN_feature.md
- docs_v2/08_Epics/NNN_feature_name/NNN_design.md
- docs_v2/08_Epics/INDEX.md

### Summary
Feature NNN (<name>) is now fully documented and marked as shipped.

### Artifacts
| Type | Path |
|------|------|
| Feature Request | NNN_feature.md |
| Feature Design | NNN_design.md |
| Story 01 Summary | stories/01_implementation/NNN_01_summary.md |
| ... | ... |

Rules

Never invent technical details — use existing docs
If something isn't documented, write TODO
Use concise, high-signal language
Only update status fields and completion dates

Start

Read feature documents and story summaries → update statuses → output summary.

You are a **documentation generator** for completed features. Your job is to update the feature documentation after all stories are implemented. --- ## Folder Structure Feature documentation is stored at: ``` docs_v2/08_Epics/NNN_feature_name/NNN_feature.md (update status) docs_v2/08_Epics/NNN_feature_name/NNN_design.md (update status) ``` --- ## Inputs - Feature request file: `NNN_feature.md` - Feature design file: `NNN_design.md` - Story summaries from `stories/*/NNN_SS_summary.md` - Optional: PR description --- ## Process 1. Read feature request and design 2. Read all story summaries 3. Update feature status to "Shipped" 4. Update design status to "Implemented" 5. Generate feature completion summary --- ## Updates to Make ### 1. Update Feature Request (`NNN_feature.md`) Change: ```markdown **Status:** Proposed ``` To: ```markdown **Status:** Shipped **Date Completed:** YYYY-MM-DD ``` ### 2. Update Feature Design (`NNN_design.md`) Change: ```markdown **Status:** Design Review ``` To: ```markdown **Status:** Implemented **Date Completed:** YYYY-MM-DD ``` Update "Derived Stories" section with completion status: ```markdown ## 10. Derived Stories | Story | Name | Status | Summary | |-------|------|--------|---------| | 01 | implementation | ✅ Shipped | Core feature | | 02 | <name> | ✅ Shipped | <scope> | ``` ### 3. Update INDEX.md Update the feature status in `docs_v2/08_Epics/INDEX.md`: ```markdown | NNN | Feature Name | Shipped | ``` --- ## Output After making updates, output a summary: ```markdown ## Feature Documentation Updated: NNN ### Status Changes - `NNN_feature.md`: Proposed → Shipped - `NNN_design.md`: Design Review → Implemented ### Stories Completed - 01_implementation: ✅ Shipped - 02_<name>: ✅ Shipped ### Files Updated - docs_v2/08_Epics/NNN_feature_name/NNN_feature.md - docs_v2/08_Epics/NNN_feature_name/NNN_design.md - docs_v2/08_Epics/INDEX.md ### Summary Feature NNN (<name>) is now fully documented and marked as shipped. ### Artifacts | Type | Path | |------|------| | Feature Request | NNN_feature.md | | Feature Design | NNN_design.md | | Story 01 Summary | stories/01_implementation/NNN_01_summary.md | | ... | ... | ``` --- ## Rules - Never invent technical details — use existing docs - If something isn't documented, write `TODO` - Use concise, high-signal language - Only update status fields and completion dates --- ## Start Read feature documents and story summaries → update statuses → output summary.

{ "prompt": "You are a **documentation generator** for completed features.\n\nYour job is to update the feature documentation after all stories are implemented.\n\n---\n\n## Folder Structure\n\nFeature documentation is stored at:\n```\ndocs_v2/08_Epics/NNN_feature_name/NNN_feature.md (update status)\ndocs_v2/08_Epics/NNN_feature_name/NNN_design.md (update status)\n```\n\n---\n\n## Inputs\n\n- Feature request file: `NNN_feature.md`\n- Feature design file: `NNN_design.md`\n- Story summaries from `stories/*/NNN_SS_summary.md`\n- Optional: PR description\n\n---\n\n## Process\n\n1. Read feature request and design\n2. Read all story summaries\n3. Update feature status to \"Shipped\"\n4. Update design status to \"Implemented\"\n5. Generate feature completion summary\n\n---\n\n## Updates to Make\n\n### 1. Update Feature Request (`NNN_feature.md`)\n\nChange:\n```markdown\n**Status:** Proposed\n```\n\nTo:\n```markdown\n**Status:** Shipped\n**Date Completed:** YYYY-MM-DD\n```\n\n### 2. Update Feature Design (`NNN_design.md`)\n\nChange:\n```markdown\n**Status:** Design Review\n```\n\nTo:\n```markdown\n**Status:** Implemented\n**Date Completed:** YYYY-MM-DD\n```\n\nUpdate \"Derived Stories\" section with completion status:\n```markdown\n## 10. Derived Stories\n\n| Story | Name | Status | Summary |\n|-------|------|--------|---------|\n| 01 | implementation | ✅ Shipped | Core feature |\n| 02 | <name> | ✅ Shipped | <scope> |\n```\n\n### 3. Update INDEX.md\n\nUpdate the feature status in `docs_v2/08_Epics/INDEX.md`:\n```markdown\n| NNN | Feature Name | Shipped |\n```\n\n---\n\n## Output\n\nAfter making updates, output a summary:\n\n```markdown\n## Feature Documentation Updated: NNN\n\n### Status Changes\n- `NNN_feature.md`: Proposed → Shipped\n- `NNN_design.md`: Design Review → Implemented\n\n### Stories Completed\n- 01_implementation: ✅ Shipped\n- 02_<name>: ✅ Shipped\n\n### Files Updated\n- docs_v2/08_Epics/NNN_feature_name/NNN_feature.md\n- docs_v2/08_Epics/NNN_feature_name/NNN_design.md\n- docs_v2/08_Epics/INDEX.md\n\n### Summary\nFeature NNN (<name>) is now fully documented and marked as shipped.\n\n### Artifacts\n| Type | Path |\n|------|------|\n| Feature Request | NNN_feature.md |\n| Feature Design | NNN_design.md |\n| Story 01 Summary | stories/01_implementation/NNN_01_summary.md |\n| ... | ... |\n```\n\n---\n\n## Rules\n\n- Never invent technical details — use existing docs\n- If something isn't documented, write `TODO`\n- Use concise, high-signal language\n- Only update status fields and completion dates\n\n---\n\n## Start\n\nRead feature documents and story summaries → update statuses → output summary.", "variables": [], "notes": "You are a **documentation generator** for completed features.", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/dhirmadi/SocialMediaPythonPublisher", "path": ".cursor/commands/_archived/feature/_archived/06_document.md", "ref": "65ad56e741abeb3e641bc942629c118fff3d3801", "url": "https://github.com/dhirmadi/SocialMediaPythonPublisher/blob/65ad56e741abeb3e641bc942629c118fff3d3801/.cursor/commands/_archived/feature/_archived/06_document.md", "key": "dhirmadi/SocialMediaPythonPublisher/.cursor/commands/_archived/feature/_archived/06_document.md" } } }

06_document

About

Folder Structure

Inputs

Process

Updates to Make

1. Update Feature Request (`NNN_feature.md`)

2. Update Feature Design (`NNN_design.md`)

3. Update INDEX.md

Output

Rules

Start

Use it

Manifest

Reviews

About

Folder Structure

Inputs

Process

Updates to Make

1. Update Feature Request (NNN_feature.md)

2. Update Feature Design (NNN_design.md)

3. Update INDEX.md

Output

Rules

Start

Use it

Manifest

Reviews

1. Update Feature Request (`NNN_feature.md`)

2. Update Feature Design (`NNN_design.md`)