Plan and document DataSpoke features within the spec/ hierarchy.
npx skills add https://github.com/selhorys/dataspoke-baseline --skill plan-doc
Please help me install this Agent Skill. Skill: plan-doc Source: https://github.com/selhorys/dataspoke-baseline/tree/main/.claude/skills/plan-doc Command: npx skills add https://github.com/selhorys/dataspoke-baseline --skill plan-doc
Write specification or planning documents for DataSpoke features, components, and architectural decisions in the spec/ hierarchy, ensuring consistent structure and alignment with the MANIFESTO and ARCHITECTURE guidelines.
Create a new spec/feature/spoke/<FEATURE>.md using the template in spec/ and start with a concise overview of goals.
High-intent search queries and answers about installing and using this skill.
Standardize feature specification documentation by applying a frontmatter-driven schema and required section headers like 'What problem does it solve?' within the spec/ directory. This ensures architectural alignment and consistent document placement.
Route planning documents by determining the correct destination folder, placing feature designs under spec/feature or spec/feature/spoke. This enforces structural governance and maintains accurate cross-references for architectural relationships.
Write a DataSpoke feature plan by reading context, determining the destination folder, writing the document using a timeless template, and updating cross-references. This ensures alignment with MANIFESTO and ARCHITECTURE guidelines.
Required sections for documenting architecture decisions include 'What problem does it solve?', 'Core Features & Use Cases', and 'Quick Start'. This frontmatter-driven schema provides a consistent layout for feature and spoke documentation.
No specific external dependencies are required to create standardized templates for feature documentation. The process relies solely on organizing content within the spec/ hierarchy using a structured, frontmatter-driven schema.
Planning documents lack cross-references when the final step of updating architecture relationships is skipped. After writing the document under spec/feature or spec/feature/spoke, you must manually update cross-references to reflect dependencies.
erikshaferCreate new CritterCab skills using a structured SKILL.md template.
rikdcConverts design documents into technical specifications with data models and API contracts.
shynlee04Coordinate delegation, validation, and anchoring for hierarchical AI governance in code projects.
Steve-Smith-CODEManage and synchronize project-wide architectural constitutions and development templates.
