Generate engineering port artifacts for migrating frontend features to React.
npx skills add https://github.com/Scripsteam/scrips-stack --skill port-spec
Please help me install this Agent Skill. Skill: port-spec Source: https://github.com/Scripsteam/scrips-stack/tree/main/port-spec Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill port-spec
Port-spec solves the challenge of documenting and orchestrating engineering porting work when moving a live feature from one frontend stack to another, ensuring all stakeholders have a consistent, testable contract.
Execute port-spec as part of the feature porting workflow to generate engineering-port artifacts and capture cross-team inputs.
High-intent search queries and answers about installing and using this skill.
To document feature porting specs, you need structured artifacts like flow diagrams, state machines, and API contracts. Port-spec generates these engineering files by integrating design, backend, Confluence, and live frontend audit inputs to ensure a testable cross-team migration contract.
Yes, a structured port specification applies to migrating live features from Flutter, Razor, or Vue to React. It defines the port scope, validation, and sequencing required to guide implementation across different frontend technologies while tracing source provenance.
Orchestrating a frontend feature migration requires flow.md, state-machine.md, api-contract.md, and gaps.md. These engineering flow artifacts capture cross-team inputs and keep missable gaps visible, culminating in a Stage 03 review packet for stakeholder alignment.
Yes, port spec generation integrates Confluence documentation, backend data, design inputs, and live frontend audit findings. It traces these Stage 01 sources to ensure all stakeholders have a consistent, testable contract during the feature migration process.
The best way to capture missable gaps is to generate a dedicated gaps.md artifact using a structured port blueprint. By tracing inputs from Stage 01 sources and live frontend audits, it keeps cross-team provenance visible throughout the migration.
An engineering port blueprint is needed to define port scope, validation, and sequencing for live feature migrations. It ensures all stakeholders have a consistent, testable contract, preventing undocumented behavior when moving features between frontend technologies.
CES-LtdExtract design tokens, components, and architecture diagrams from codebases and UI assets.
paultyngEvaluate implementation plans and issue READY, NEEDS_REVISION, or BLOCKED verdicts with prioritized findings.
cedricfarinazzoScan Confluence and Jira to create a formal ADR with context, data model, API, and deployment considerations.
jrodrigopucaGenerate architecture documentation with Mermaid diagrams and module descriptions.
