z1-test
Official@z1-test
Standardizes product requirements, Gherkin behavior specifications, and GitHub lifecycle management through structured documentation and issue governance.
Agent Skills by z1-test
Showing 11 vetted skills indexed across 2 GitHub repositories.
code-documentation
Enforce consistent documentation style for code elements like functions and classes.
github-pr-flow
Automate GitHub pull request lifecycle from branch creation to merge.
feature-roadmap-decomposition
Decompose Product Requirements Documents into feature lists with explicit dependencies.
change-maintenance-specification
Generate structured change specification documents for feature modifications.
gherkin-authoring
Create executable behavior specifications using Gherkin Given/When/Then syntax.
prd-authoring
Generate structured Product Requirements Documents with problem clarity and trade-offs.
github-kernel
Define foundational rules and safety boundaries for GitHub interactions.
github-issues
Automate GitHub Issues creation, updates, milestones, and sub-issues via REST API.
feature-specification
Create feature specifications in Gherkin syntax within Markdown format.
ambiguity-detection
Detect critical ambiguities in product requirements documents and generate structured clarification questions.
markdown
Codify Markdown/MDX documentation conventions with frontmatter and Mermaid diagrams.
Frequently Asked Questions About z1-test
FAQPage SchemaWhat specific tasks are enabled by these capabilities?▼
These capabilities enable the systematic decomposition of product requirements, the generation of Gherkin-based behavior specifications, and the structured management of GitHub issues and pull request lifecycles. It ensures technical clarity through ambiguity detection and standardized documentation practices.
Which personas benefit from these technical skills?▼
Product managers, technical leads, and software engineers benefit from these skills. They are designed for teams requiring rigorous alignment between product requirements, behavior-driven development specifications, and repository-level issue tracking.
What are the prerequisites for implementing these specifications?▼
Implementation requires a repository environment utilizing GitHub for version control and issue management. Users must adopt Markdown for documentation and adhere to Gherkin syntax for behavior specifications to ensure compatibility with the provided governance and decomposition frameworks.