Generate incremental features, acceptance tests, and development slices per BRIDGE v2.1.
npx skills add https://github.com/etapsc/bridge --skill bridge-feature
Please help me install this Agent Skill. Skill: Bridge Feature Source: https://github.com/etapsc/bridge/tree/main/bridge-codex/.agents/skills/bridge-feature Command: npx skills add https://github.com/etapsc/bridge --skill bridge-feature
This Skill automates the generation of incremental requirements for an existing project, ensuring continuity and adherence to the BRIDGE methodology.
requirements.json, context.json, and human-playbook.md to maintain project continuity.Use the bridge feature skill to generate new requirements for the project.
High-intent search queries and answers about installing and using this skill.
Generating incremental requirements for an existing agile project involves creating new features, acceptance tests, and development slices based on current artifacts. This maintains continuity by updating project state files like requirements.json and context.json.
The BRIDGE methodology for incremental development provides a structured approach to generating features, acceptance tests, and development slices. It ensures project continuity by systematically managing state across requirements, context, and human playbooks.
Managing project state when adding new development slices requires loading and updating specific artifacts like requirements.json, context.json, and human-playbook.md. This tracks progress and maintains continuity across incremental feature additions.
Yes, using the BRIDGE methodology requires existing project artifacts to generate incremental features accurately. The process relies on adhering to existing ID schemes and updating established state files to ensure seamless integration into your development workflow.
Acceptance tests in incremental feature generation define the specific criteria a new feature must meet. They are generated alongside development slices to provide clear validation steps before implementation begins in your existing project environment.
JHaugaardResolve architectural ambiguity in project briefs and generate architecture-context.json.
jaisonerickImplement story files into tested code and update execution logs.
CygnusfearUpdate project documentation to reflect the current codebase state.
hoonsubinGenerate GitHub issues from Epic, Feature, Story, Enabler, and Test hierarchies.