Loading...
Loading...
Found 17 Skills
Set a tracking document as the source of truth for the current feature or task. Use when starting work on a feature, bug fix, or multi-step task that benefits from a persistent record of decisions, discoveries, and progress. Keeps the document updated as work proceeds.
/cs:founder-mode <question> — Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point.
Expertise in maintaining persistent bot memory, synchronizing with previous sessions via the Task Ledger, and preserving decision logs.
Write and maintain a CHANGELOG that stays useful months later — as a decision log, not a commit dump. Use when setting up a changelog for a project; after any code change in a project that has one; when preparing a release; or when the user asks why something was built the way it is and the answer is not in the code. Do not use for commit messages, PR descriptions, or user-facing release notes — those are different formats with different readers.
1. Requirement Gathering