Standardize technical design documents with scope validation and assumption recording.
npx skills add https://github.com/bostonaholic/team --skill authoring-designs
Please help me install this Agent Skill. Skill: authoring-designs Source: https://github.com/bostonaholic/team/tree/main/skills/authoring-designs Command: npx skills add https://github.com/bostonaholic/team --skill authoring-designs
This skill addresses the inconsistency and ambiguity in technical design documentation by enforcing a rigorous, standardized authoring procedure that ensures scope validation and autonomous resolution of design trade-offs.
Ask the team agent to draft a new design document for the proposed feature using the authoring-designs skill.
High-intent search queries and answers about installing and using this skill.
You can standardize technical design documents by enforcing scope validation against repository boundaries and cross-service dependencies, ensuring consistent structure and preventing scope creep across complex engineering tasks.
Autonomous assumption recording resolves open design questions by documenting trade-offs and assumptions during technical writing, ensuring human reviewers can audit the logic and decision-making process during PR review.
Drafting design docs for cross-repository coordination requires applying structured templates that enforce scope validation, document current and desired end states, and rigorously analyze edge cases using standardized technical writing rules.
Writing design docs with ASD-STE100 Simplified Technical English works for complex systems by reducing ambiguity and enforcing rigorous, standardized authoring procedures for cross-repository software engineering tasks.
You need a standardized template for software architecture documentation when tackling complex engineering tasks requiring cross-repository coordination, rigorous edge-case analysis, and auditable autonomous resolution of design trade-offs.
The limitation of autonomous decision making in design docs is that it requires human reviewers to actively audit recorded assumptions and trade-offs during PR review to validate the autonomous logic and scope boundaries.
wesleyegbertoDefine service boundaries for distributed systems using domain-driven design.
CarbeneAIReview product plans in four modes to challenge assumptions and recommend scope changes.
zcaceresEnforce ASD-STE100 Simplified Technical English writing constraints via session hooks.
miles990Convert game ideas into structured Master and Feature Documents.
