Loading...
Loading...
Found 2 Skills
Draft or update architecture documents under `easysdd/architecture/` — describe what a subsystem/module looks like currently, how it is divided, and how external interfaces operate, to provide pre-positioning input for subsequent feature-design. Information sources include code + user materials (oral accounts, scattered documents, compound deposits, existing decisions), and the output can be reverse-validated by anchoring to specific `file:line`. Two modes: new (draft a new architecture document from scratch), update (refresh an existing document based on the latest code status and new user materials). Single-target rule — only modify one document at a time. Trigger scenarios: user says "fill in an architecture doc", "draft an architecture document", "update the architecture directory", "write down the structure of this module", or when it is found that "something that should be in the architecture is missing" during the feature-design / feature-acceptance phase.
The root skill of the easysdd workflow family — introduces the workflow system and routes users to the correct sub-skill. Trigger scenarios: Users mention "easysdd", "sdd", "spec-driven", "how to use this set of processes", "which skill should I use", "where to start", or describe a new feature but haven't decided on the entry stage. Known intents (brainstorm/design/implementation/acceptance/BUG/exploration, etc.) will trigger the corresponding sub-skill first instead of this skill.