ins-enco
Official@ins-enco
Standardized feature specification and technical requirement lifecycle management for engineering teams using structured design artifacts and dependency-ordered task generation.
Agent Skills by ins-enco
Showing 9 vetted skills indexed across 1 GitHub repositories.
ins-encospeckit-checklist
Generate unit-test-style checklists validating feature requirement quality.
ins-encospeckit-constitution
Replace ALL_CAPS placeholders in .specify/memory/constitution.md and synchronize dependent templates.
ins-encospeckit-implement
Execute implementation plans from tasks.md and plan.md with hooks and checklist gating.
ins-encospeckit-taskstoissues
Convert design tasks into dependency-ordered GitHub issues.
ins-encospeckit-clarify
Identify underspecified areas in feature specs and generate prioritized clarification questions.
ins-encospeckit-plan
Generate implementation plans and design artifacts from spec-kit templates.
ins-encospeckit-analyze
Analyze spec.md, plan.md, and tasks.md for inconsistencies and coverage gaps.
ins-encospeckit-specify
Generate template-based feature specs and create feature branches from natural language descriptions.
ins-encospeckit-tasks
Generate dependency-ordered tasks.md from spec-kit design artifacts.
Frequently Asked Questions About ins-enco
FAQPage SchemaWhat specific tasks can be performed using these capabilities?▼
These capabilities enable the generation of feature specifications, validation of requirement quality via unit-test-style checklists, identification of underspecified design areas, and the conversion of design artifacts into dependency-ordered issue tracking tickets.
Which personas benefit most from these technical requirements?▼
Software engineers, technical leads, and product managers benefit by utilizing these functions to maintain consistency between feature specifications, implementation plans, and task tracking, ensuring high-quality requirement coverage throughout the development lifecycle.
What are the prerequisites for implementing these design artifacts?▼
Implementation requires the presence of standard design files including spec.md, plan.md, and tasks.md within the repository. Users must maintain the .specify/memory/constitution.md file to ensure template synchronization and proper execution of requirement gating.