Orchestrates project-status governance across ROADMAP, POLICY, HEALTH, and CHANGELOG files.
npx skills add https://github.com/nonlinear/skills --skill backstage
Please help me install this Agent Skill. Skill: backstage Source: https://github.com/nonlinear/skills/tree/main/backstage-skill Command: npx skills add https://github.com/nonlinear/skills --skill backstage
Backstage provides a centralized, rule-driven workflow to manage project status and governance across ROADMAP, POLICY, HEALTH, and CHANGELOG, reducing drift and misalignment between reality and documentation.
Run backstage start to initialize the project context and begin backstage session management.
High-intent search queries and answers about installing and using this skill.
You can align project documentation with actual development status by running health checks that synchronize ROADMAP, POLICY, HEALTH, and CHANGELOG files across multi-repo workspaces. This governance workflow reads the README navigation block to keep documentation and reality in sync.
The best way to enforce project governance and quality before commits is to use a centralized, rule-driven status cockpit. It applies context switching and proactive collaboration to ensure consistent rules and visibility across epic planning and project setup.
To set up a project health check workflow for epic planning, initialize the project context by running the start command. This begins session management, loads context automatically without hardcoded paths, and runs health checks to enforce quality across your workspaces.
Yes, you can use this governance workflow in a multi-repo workspace without hardcoding file paths. It dynamically reads the README navigation block to locate status files, ensuring flexible project setup and health enforcement across various repository structures.
Project documentation drifts from reality in multi-repo workspaces due to decentralized status updates and lack of rule-driven enforcement. Applying trigger-driven workflows across ROADMAP and CHANGELOG files reduces this misalignment by automating documentation synchronization.
You need a centralized status cockpit for project management when orchestrating epic planning and quality enforcement across multiple repositories. It provides unified governance over ROADMAP, POLICY, HEALTH, and CHANGELOG status files to prevent documentation drift.
maestria-coBootstrap per-project agent context across a VS Code multi-root workspace.
jperezdelrealEnforce in-commit test updates when APIs or public interfaces change.
HigorAlvesDetect multi-repo workspaces and manage synchronized branching and pull request linking.
Hypercart-Dev-ToolsValidate project documentation standards and repository state consistency via shell utilities.
