Search OpenSpec explanation records by keyword, tag, or feature.
npx skills add https://github.com/fjpulidop/specrails-core --skill why
Please help me install this Agent Skill. Skill: why Source: https://github.com/fjpulidop/specrails-core/tree/main/specrails-plugin/skills/why Command: npx skills add https://github.com/fjpulidop/specrails-core --skill why
This skill enables teams to locate and interrogate explanation records produced by sr-architect, sr-developer, and sr-reviewer during the OpenSpec implementation pipeline, enabling faster reasoning traceability.
Run /specrails:why to list recent explanation records or search with /specrails:why <query> to find specific rationale.
High-intent search queries and answers about installing and using this skill.
Search explanation records in the OpenSpec pipeline by running a query with keywords, tags, or features to surface relevant decisions. The skill retrieves these in-context records and provides concise summaries of the rationale generated during implementation.
Trace architectural decisions by querying the explanation records produced by sr-architect, sr-developer, and sr-reviewer. The skill surfaces these in-context records to enable faster reasoning traceability and provides summaries suitable for architecture reviews.
Retrieve recent in-context explanations by listing the latest explanation records generated during the implementation pipeline. The skill surfaces these records and returns them in a consistent, readable format suitable for decision traceability reviews.
Yes, you can query specific features within explanation records by providing a targeted search query. The skill identifies and retrieves the most relevant records matching those features and summarizes the decisions and rationale for faster reviews.
Yes, the skill operates without external dependencies to query decision rationale. It directly accesses and interrogates the explanation records generated during the OpenSpec implementation pipeline to surface summaries of decisions.
Implementation pipeline records may not show in search results if the query keywords, tags, or features do not match the generated explanation records. Refine the search terms to accurately target the rationale and decisions captured during the pipeline phases.
fjpulidopSearch explanation records from specrails agents by keyword or tag.
growilabsReview technical design documents and issue a GO/NO-GO decision.
tanghuoGuide users to select appropriate sr-* skills for workflows.
Yogi-076Search and analyze JSONL session logs by date, user, or keyword.
