Align code changes with approved PRODUCT.md and TECH.md specs.
npx skills add https://github.com/lalaABC/waprcn --skill implement-specs-lalaabc
Please help me install this Agent Skill. Skill: implement-specs Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/implement-specs Command: npx skills add https://github.com/lalaABC/waprcn --skill implement-specs-lalaabc
This skill provides a disciplined workflow to implement features described in approved product and tech specs, ensuring code changes stay in sync with the documented design and that specs guide the implementation and later updates.
Review the approved PRODUCT.md and TECH.md, then implement the feature in a single PR with aligned specs, code, and tests.
High-intent search queries and answers about installing and using this skill.
To align code with specs, you implement features in a single PR while referencing approved PRODUCT.md and TECH.md files. This disciplined workflow enforces prerequisites and procedures, ensuring documentation and implementation stay in sync as decisions evolve.
To keep specs and code in sync when requirements change, update the relevant spec files under specs/ and associate them with the corresponding PR. This ensures documentation accurately reflects evolving decisions alongside the code changes.
The best way to enforce traceability is to guide PRs using approved PRODUCT.md and TECH.md files, optionally tracking implementation checkpoints and decisions in PROJECT_LOG.md and DECISIONS.md documents to maintain a clear audit trail.
Yes, you need approved PRODUCT.md and TECH.md files before starting. The workflow enforces prerequisites by verifying these specs exist under specs/FEATURE/, ensuring implementation is guided by documented design and approved technical decisions.
To automate the implementation workflow, use a process that verifies spec prerequisites, reads PRODUCT.md and TECH.md to guide code changes, prioritizes tests, and updates specs as decisions evolve, consolidating everything into a single aligned PR.
You should not use a spec-driven implementation workflow when approved PRODUCT.md and TECH.md files do not exist or cannot be created, as the process enforces verifying these prerequisites to guide PRs and maintain documentation alignment.
89jobrienEnforces spec-first workflow for Warp features via PRODUCT.md and TECH.md files located in specs/.
abranjithReview code changes against plan and feature specifications.
etylsarinEnforce feature-branch pull request workflows and prevent direct commits to main.
tsuna44Synchronize manually edited project artifacts back into the Change Requirements Specification.
