change-writer

Assist in writing change proposals — analyze the scope of change impact, generate a structured proposal.md and a phase-based tasks.md, ensuring changes are traceable and impact is controllable.

Phase & Trigger

• Phase: Cross-phase (Delta workflow)
• Trigger conditions:
  • User has run openlogos change <slug> and wants help filling in the proposal
  • User describes a need to modify, add, or remove a scenario/feature
  • User mentions “change proposal”, “iteration”, “requirement change”

Prerequisites

1. Project is initialized (logos/logos.config.json exists)
2. Change proposal directory exists (logos/changes/<slug>/)
3. Main documents in logos/resources/ are readable

If prerequisites are not met, the user must first run openlogos change <slug>.

What It Does

1. Understand the user’s intended change (what, why, which scenarios)
2. Scan existing documents in logos/resources/ to identify the full affected scope
3. Determine the change type based on propagation rules
4. Generate a compliant proposal.md
5. Automatically break down tasks.md by change type
6. Provide a ready-to-use prompt for chain-driven execution

Change Types and Propagation

Change Type	Minimum Updates Required
Requirement-level	Full chain: Requirements → Design → Architecture → API/DB → Tests → Code
Design-level	Prototypes + Scenarios + API/DB + Tests + Code
Interface-level	API/DB + Tests + Code
Code-level fix	Code + Re-verification

Impact Analysis Scope

The Skill scans all document layers to identify affected artifacts:

1. Requirement documents (prd/1-product-requirements/) — scenario definitions
2. Product design (prd/2-product-design/) — feature specs and prototypes
3. Technical plans (prd/3-technical-plan/) — sequence diagrams
4. API documents (api/) — affected endpoints
5. DB documents (database/) — affected table structures
6. Test cases (test/) — affected test cases
7. Orchestration tests (scenario/) — affected orchestration files

Generated Files

proposal.md

# Change Proposal: [Change Name]

## Reason for Change
## Change Type
## Change Scope
- Affected requirement documents: [list]
- Affected functional specs: [list]
- Affected business scenarios: [scenario ID list]
- Affected APIs: [endpoint list]
- Affected DB tables: [table list]
- Affected test cases: [list]

## Change Summary

tasks.md

A phase-based checklist where only affected phases are listed:

# Implementation Tasks

## Phase 1: Document Changes
- [ ] Update acceptance criteria for S0x

## Phase 2: Design Changes
- [ ] Update interaction design for S0x

## Phase 3: Technical Changes
- [ ] Update sequence diagram for S0x
- [ ] Update API YAML
- [ ] Validate API YAML (all special chars double-quoted)
- [ ] Update DB DDL
- [ ] Update test cases
- [ ] Implement code changes

Chain-Driven Execution

After generating the proposal, the Skill provides a ready-to-use prompt so the user can kick off sequential task execution:

• Multi-phase changes: “Follow tasks.md and help me progressively update all affected documents for S0x”
• Code-level fixes: “Help me fix [issue] for S0x and re-verify”

The AI reads tasks.md, executes items sequentially, reports after each task, and prompts “Continue to the next item?”

Outputs

File	Location
proposal.md	logos/changes/<slug>/proposal.md
tasks.md	logos/changes/<slug>/tasks.md

Best Practices

• Overestimate the impact scope — missing one link is more dangerous than double-checking
• Change type determines workload — help users understand before starting
• Follow the process even for small changes — “just one API line” may affect tests and code
• tasks.md is the execution checklist — check off items with [x] as they complete

Related Skills

• After tasks complete: merge-executor — merge deltas into main documents
• After merge: Run openlogos archive <slug> to archive the proposal