About this AI skill
The Change log skill is pre-built for Elle (the AI assistant in Aha! software) and reads every comment — including replies — on a release, epic, feature, initiative, or idea. It produces a chronological change log with dates, decisions, recorded rationale, owners, and related records, along with a summary of how the work changed. Separate sections identify reversed decisions, unresolved questions, and decisions with no recorded rationale.
The full Change log skill skill, as Elle uses it:
# Change log
Use after a review cycle, a development cycle, or release readiness, when a record has collected enough comments that the decisions in it are hard to find.
## Definitions
Use these meanings consistently in every step.
- **Record:** The release, feature, epic, initiative, or idea being reviewed, or the record whose link the user pasted into the chat
- **Decision:** A choice that changed the direction of the work: scope added or cut, an approach chosen, a date moved, or a trade-off accepted
- **Rationale:** Why the decision was made, taken from the comment thread rather than inferred
- **Owner:** The person who made the decision or who is accountable for what follows from it
## Workflow
1. Read every comment on the record in chronological order, including replies. Order is what makes a reversal visible.
2. Identify the decisions. Distinguish them from discussion. A question with no answer is an open item, not a decision.
3. Capture the date, the decision, the rationale, and the owner for each one. Take the owner from who stated the decision, not from who commented most.
4. Link each decision to the records it affected, when the thread names them
5. Identify reversals and supersessions. When a later decision overturns an earlier one, show both and mark which stands.
6. List open items: questions raised and never resolved in the thread
7. Flag decisions whose rationale is not recorded, rather than inventing one
8. Order the log chronologically, then summarize the through line in a few sentences.
## Rules
- If the record has no comments, say so rather than producing an empty log
- Take the rationale from the thread. When it is absent, write **Rationale not recorded** and move on.
- Attribute an owner only when the thread makes it clear
- Show reversals rather than silently keeping the latest decision
- Reference every record by reference number and name
- Do not edit comments or update the record. Present the log and let the user apply it.
- Headers use sentence case. No em dashes, en dashes, or curly quotes.
## Output
```
## Summary
<how the work changed over the period, in three to five sentences>
## Change log
| Date | Decision | Rationale | Owner | Related records |
## Reversals
- <earlier decision, later decision, and which stands>
## Open items
- <question raised and never resolved, and who raised it>
## Missing rationale
- <decision recorded without a stated reason>
```
## Quality checks
- Every entry has a date and comes from an actual comment
- Discussion is separated from decisions
- Reversals show both decisions rather than only the latest
- No rationale is inferred where the thread does not state oneTry this AI skill now
Open the Change log skill in Aha! Roadmaps to turn a record's comment thread into a log of product decisions.
Open this AI skillAbout Elle
Elle , the AI assistant in Aha! software, helps product teams accelerate product work by creating content, analyzing records, and updating plans using information in their account. The AI prompt library offers pre-built skills and tasks for Elle that are tuned for product development work.