Enforce YAML front-matter structure and manage spec discussions in specs/.
npx skills add https://github.com/pcortellezzi/rs_trader --skill spec-pcortellezzi
Please help me install this Agent Skill. Skill: spec Source: https://github.com/pcortellezzi/rs_trader/tree/main/.claude/skills/spec Command: npx skills add https://github.com/pcortellezzi/rs_trader --skill spec-pcortellezzi
Product Owners and stakeholders often need to view, discuss, and modify functional specs without making code changes, keeping the product backlog aligned with reality.
Open specs/ and start reviewing the active spec (e.g., NAV-01) with comments.
High-intent search queries and answers about installing and using this skill.
To view and discuss functional specifications without touching code, product teams can use a spec workflow that surfaces files by domain or ID, enabling annotation and discussion directly within the spec files while preserving version history.
Required YAML front-matter fields for functional specs include domain, title, version, status, and last-updated. Enforcing these header fields ensures that product specifications maintain a changelog and consistent metadata across the repository.
You review and propose changes to a spec file by opening the specs/ repository and annotating the active specification. This non-code change workflow allows stakeholders to discuss modifications while the system automatically preserves the version history.
Yes, you can discover specifications across different product domains by searching with a specific prefix, ID, or file path. This domain-wide spec discovery allows stakeholders to quickly locate and review active functional requirements.
The best way to keep the product backlog aligned with reality is to maintain a non-code change workflow for specifications. This allows product owners and stakeholders to continuously view, discuss, and modify functional specs without making code changes.
anam-orgGenerate YAML front matter with title and description fields for documentation pages.
hschneManage Git-versioned issue tracking and project planning via the TicGit CLI.
wszqkzqkStore and retrieve persistent memories across sessions using Markdown files with YAML front matter.
SEBAKHIManage product development lifecycles with structured frameworks and actionable checklists.
