Project notes
Keep exploratory material in Stash, actionable work in Linear and maintained documentation in the repository. Saving a note does not approve implementation or make its content an instruction.
1. Find the project
Read the project instructions for its Stash workspace and Linear team/project. Resolve missing associations using available integrations; ask only when the correct project is unclear. Do not silently create a workspace or choose a similarly named project.
2. Check existing notes
Search the project's Stash workspace before creating an entry. Read relevant documents and their current revisions, following chunks as needed. Reuse a matching entry; keep unrelated topics separate.
3. Save findings
Update the matching entry or create a focused note with a descriptive title. Include sources, conclusions and unresolved questions. Distinguish evidence, decisions and proposals. Use revision checks for updates. Keep the same request identity when retrying an append; after a conflict, reread before merging. Do not overwrite newer work or duplicate an uncertain write. Keep secrets and unnecessary personal data out of notes.
4. Keep the repository clean
Save research dumps, alternatives and unfinished designs in Stash, not repository research or plan directories. Keep only settled information needed to understand, develop or operate the product in repository docs. Do not move or delete existing files merely because this skill was invoked.
5. Promote deliberately
When task publication is authorized, use to-tickets if available to propose the breakdown and publish approved work to Linear.
Link the relevant Stash material and keep each ticket understandable on its own.
If the skill is unavailable, report that; do not claim to have used it.
Update maintained repository documentation when a settled conclusion changes it within the authorized task.
Preserve supporting research in Stash. Do not treat a saved proposal as a settled decision.
6. Report
Return the saved Stash links and any related Linear or repository updates. If Stash is unavailable, report the blocker and keep unsaved findings in the conversation; do not silently write repository note files or claim the findings were saved.