Manages project folders and topic files for planning and execution workflows.
npx skills add https://github.com/alatyshau/duet --skill topic-master-alatyshau
Please help me install this Agent Skill. Skill: topic-master Source: https://github.com/alatyshau/duet/tree/main/packages/skills/tools/topic-master Command: npx skills add https://github.com/alatyshau/duet --skill topic-master-alatyshau
topic_*.md files with six mandatory sections (Motivation, Links, Narrative, Open Questions, Outputs, Implementation Plan). - Project Folder Organization: Organizes topics into ЯДРО (core), ОРБИТА (orbit), and АРХИВ (archive) categories within project folders indexed by index.md. - Planning Workflow: Enforces a Step 0 planning phase where open questions are resolved before implementation steps begin, with each step sized to one commit. - Use Case: When starting a new feature investigation, create a topic file capturing the problem, explore open questions in dialogue mode, then commit the planning document before writing any code. ## Quick Start Ask the AI to create a new topic file for your current problem following the canonical topic file format with all six sections.High-intent search queries and answers about installing and using this skill.
A topic file contains six mandatory H2 sections in strict order: Motivation, Links, Narrative, Open Questions, Outputs, and Implementation Plan. The Implementation Plan must include a problem statement, completion criteria, and steps starting with Step 0 for planning documentation.
A project folder represents one mission, while a topic is a direction of work within that mission. Use the litmus test: if the topic can be added to the folder's roadmap, it stays as a topic; if it has a separate mission, create a new folder.
Topics describe where the project is going (plans, temporary), while spec files describe where it is now (implemented, source of truth). For completed steps read spec first; for pending steps read the topic first.
A topic moves to АРХИВ when it is completed or a final decision has been made. The file is renamed with a YYMMDD_ prefix and the index.md records a summary of the outcome.
Topic files require disciplined maintenance across dialogue, planning, and execution modes with different write permissions. They are not suited for tracking implemented behavior, which belongs in spec files as the source of truth.
sergio-bershadskyExtract participants, topic, decisions, and action items into structured Markdown documents.
vZulinExecute predefined tasks.md plans with TDD-aligned sequential and parallel steps.
ribon-orgUpdate DESIGN.md with decisions extracted from conversation content.
SanHsienDecomposes specs into ordered, verifiable implementation tasks with acceptance criteria.