// Track context across sessions for long-running features. Use when starting multi-session work, checkpointing progress, or resuming work on a feature tracked in a GitHub issue.
Conventions for authoring Rust code in the Dada compiler. Use when writing or modifying Rust code, adding functions, or making implementation changes.
RFC and specification workflow for Dada language features. Use when working with RFCs, writing spec paragraphs, or tracking implementation progress.
Run and interpret Dada test results. Use when running tests, debugging test failures, or understanding test output.
Write spec-aligned Dada tests. Use when creating new test files, organizing tests to match the specification, or adding test coverage for language features.
| name | tracking-issues |
| description | Track context across sessions for long-running features. Use when starting multi-session work, checkpointing progress, or resuming work on a feature tracked in a GitHub issue. |
Use GitHub issues as living documents to maintain context across work sessions. One issue per user-facing feature.
# Find active work
gh issue list --label tracking-issue
# Check a specific issue
gh issue view <number>
Not for RFC features. RFC-tracked work uses impl.md in the RFC directory for detailed progress tracking. A GitHub issue for an RFC should just be a lightweight pointer with links to the RFC and its impl status (e.g., https://dada-lang.org/rfcs/NNNN-feature-name/impl.html).
For non-RFC work (refactors, bug investigations, infrastructure) that spans 2+ sessions or multiple code areas, use a tracking issue.
Labels: tracking-issue, ai-managed, plus type (feature, bug, refactor)
Title: Clear user-facing outcome (not "encryption work" — instead "Implement client-side encryption")
OP template (keep updated as the living summary):
# Feature Name
**Status**: Planning | In Progress | Blocked | Complete
## Current Understanding
Brief summary of what needs to be done and current approach
## Next Steps
- [ ] Specific actionable item with file:line references
- [ ] Another concrete next step
## Open Questions
- What we're still figuring out
## Context
Key background and why this work matters now
Read the issue OP to understand current state. Work from "Next Steps."
**Session summary:**
- What was attempted or explored
- Key discoveries or problems encountered
**Impact on approach:**
- How understanding changed
- New questions that emerged
**Progress:** Completed items from next steps, what's next
Set status to "Complete" and close the issue.
ai-managed