macro88/macrostack
Development workflow skills for requirements, design, planning, delivery, review and workspace hygiene.
Explore and document a software solution from agreed requirements, including architectural choices, C4 views with code-structure drill-down, interfaces, flows, and a verification approach. Use before implementation planning or when an existing design needs to change.
Implement a bounded, authorised task from agreed requirements, design and a delivery plan; verify the change and return a reviewable diff with evidence. Use for assigned implementation work or addressing review findings, stopping before integration or release.
Audit and maintain a project's documentation and temporary delivery resources. Use to consolidate completed delivery records, retire finished worktrees and task-owned scratch files, or investigate disk pressure. Preserve active work, durable evidence and project boundaries; perform cleanup only within actual authority.
Deliver an agreed plan across its phases, assigning bounded implementation, reviewing results and integrating verified changes within authority. Use for a whole planned feature or an explicitly limited phase, with workers or a single agent; planning alone does not start execution.
Turn agreed software requirements and solution design into a repository roadmap and manageable implementation phases, with dependencies and completion evidence. Use for the Plan stage, planning the next phase, or replanning affected work after a change.
Review an implemented change or pull request against agreed requirements, design and verification evidence. Use before integration or to recheck corrections; return a scoped acceptance decision and actionable findings without merging or changing the implementation.
Set up or reconcile Macrostack in a fresh or existing project after installing the skills. Establish preferences, record locations, workflow pointers and supporting-tool availability without starting product development or overwriting existing agreements.
Interview the user iteratively to resolve a software idea, feature change, or refactoring request into agreed living requirements, acceptance examples, shared vocabulary, and a handoff to solution design. Use when intent or scope needs establishing before design and implementation.