Generate concise design documents for proposed technical changes.
npx skills add https://github.com/marin-community/marin --skill design-doc-marin-community
Please help me install this Agent Skill. Skill: design-doc Source: https://github.com/marin-community/marin/tree/main/.agents/skills/design-doc Command: npx skills add https://github.com/marin-community/marin --skill design-doc-marin-community
This Skill helps you create clear, focused design documents that effectively communicate a proposed change, its rationale, and its implications without unnecessary detail.
Use the design-doc skill to write a design document for tracking step execution time in the executor framework.
High-intent search queries and answers about installing and using this skill.
To write a concise software design document, define the problem, goals, solution approach, and trade-offs. Use minimal code snippets and file:line references to keep the proposal readable and focused on core technical implications.
A technical proposal should include a structured problem definition, clear goals, an implementation outline, and future considerations. This ensures stakeholders share a complete understanding of the proposed change and its rationale.
Structure a design document by adhering to strict length and content guidelines. Emphasize concise communication by using file references and illustrative code snippets rather than extensive text to convey core ideas.
Generate a spec for a new software feature when you need to communicate a proposed change, its rationale, and its implications. It helps outline the technical approach and trade-offs without unnecessary detail.
The best way to outline implementation steps in a technical proposal is to focus on the solution approach and implementation outline. Include trade-offs and reference code using file:line numbers to maintain brevity.
Yes, the design-doc skill works without external dependencies. It generates readable design documents independently, focusing strictly on problem definition, goals, and solution approach without requiring additional modules.
akillnessConvert conversations and codebase context into a structured PRD for issue trackers.
camilooscargbaptistaConvert product requirements into executable technical specification documents.
GigaFydeVerify source code implementations against task specifications with file:line references.
Mahaboob26Create structured Markdown documentation with GitHub Flavored Markdown formatting.
